Skip to main content

Vansah MCP Rate Limits

Understand rate-limit messages when using Vansah MCP. Learn how to pause requests, reduce repeated calls and safely retry an interrupted task.

If your AI assistant reports that a rate limit has been reached, pause the task before retrying. A rate limit controls how many requests a service can process during a period of time; it does not necessarily mean your connection is broken.

Why a rate-limit message can appear

A single request to an AI assistant can require several tool calls. For example, reviewing test coverage may involve finding work items, loading Test Cases and retrieving results. Repeated searches or large tasks can generate more requests than you expect.

The message may relate to Vansah, Jira or your AI provider. Check the service named in the error before deciding what to retry.

Where to check limits

For published Vansah API capacity by edition, see Vansah Standard vs Advanced: Features and Limits. The Vansah API documentation also describes API-token usage and error messages.

Vansah MCP connects through OAuth. Do not assume that a limit documented for API-token traffic is a separate allowance for each AI assistant or MCP tool. If you need a confirmed limit for your MCP workflow, contact Vansah Support with the task and error details.

What to do when a request is limited

  1. Pause repeated attempts. Stop resending the same prompt or running the same workflow in several conversations.

  2. Follow the suggested wait time. If the error includes a retry time, wait until that time has passed.

  3. Reduce the scope. Retry with one space, requirement or Test Plan, or a smaller set of Test Cases.

  4. Check what completed. If the task creates or updates records, ask the assistant to find the saved records before repeating the action.

  5. Retry the remaining work. Resume with a smaller request. If the limit appears again, allow a longer pause before another attempt.

Example: Instead of asking for all testing information across several spaces, start with “Show the Test Cases linked to VANS-1234.” Then ask for the results or coverage you need.

Reduce unnecessary requests

  • Include exact work item keys, Test Case keys and Test Plan names.

  • Use filters such as space, release, sprint or iteration to narrow the task.

  • Work through large tasks in smaller groups and review each result before continuing.

  • Ask the assistant to use information already returned in the conversation when it is still current.

If you manage an automated workflow

An HTTP 429 Too Many Requests response indicates rate limiting. If a response provides a Retry-After value, configure the client to honor it. Otherwise, use retries with increasing delays and a maximum number of attempts.

Before retrying an action that creates or changes records, check whether it already succeeded. This helps prevent duplicate Test Cases, plans or results.

When to contact support

If the problem continues after waiting and reducing the scope, send Vansah Support the Jira site, AI client, task, time of the error and full error message. Remove access tokens, passwords and other credentials before sharing it.

Did this answer your question?