Skip to main content
Watch: I Built an AI App Without Leaving Databricks

Google Vertex AI (generative AI) error

Vertex AI 429 RESOURCE_EXHAUSTED: what it means and how to fix it

Error message
429 RESOURCE_EXHAUSTED

Retry? YesLast verified 6 documented fixes3 sources

What it means

The number of requests exceeds the capacity allocated to process them. Depending on the error message, it is caused by API quota, shared server capacity, or the daily limit for logprobs requests.

Causes

  • API quota over the limit, for example exceeding the requests per minute limit
  • Server overload due to shared server capacity
  • Reaching the daily limit for requests using logprobs
  • Acceleration limits after a sharp increase in usage

How to fix it

  1. Fix 1.

    Check the generative AI quota limits and apply for a higher quota (Quota Increase Request) if needed.

  2. Fix 2.

    Retry after a few seconds using truncated exponential backoff; the API errors page recommends retrying no more than two times with a minimum delay of one second. Contact support if the error persists for hours.

  3. Fix 3.

    Use the global endpoint instead of a regional endpoint whenever possible.

  4. Fix 4.

    Avoid traffic spikes and ramp up traffic gradually; on Standard pay-as-you-go, smoothing traffic helps.

  5. Fix 5.

    Consider purchasing Provisioned Throughput for a more consistent level of service.

  6. Fix 6.

    The Gen AI SDK retries 429 and 5xx automatically; retry behavior can be configured with HttpRetryOptions:

    Snippet
    from google import genai
    from google.genai import types
    
    client = genai.Client(
        vertexai=True,
        project=PROJECT_ID,
        location="global",
        http_options=types.HttpOptions(
            retry_options=types.HttpRetryOptions(
                initial_delay=1.0,
                attempts=5,
                http_status_codes=[408, 429, 500, 502, 503, 504],
            ),
            timeout=120 * 1000,
        ),
    )

More Vertex AI errors

All 11 Vertex AI errors

HTTP 429 at other providers

Compare 429 across providers

FAQ

What does the Vertex AI error "429 RESOURCE_EXHAUSTED" mean?

The number of requests exceeds the capacity allocated to process them. Depending on the error message, it is caused by API quota, shared server capacity, or the daily limit for logprobs requests.

How do I fix Vertex AI "429 RESOURCE_EXHAUSTED"?

There are 6 documented fixes. Start with the first: Check the generative AI quota limits and apply for a higher quota (Quota Increase Request) if needed.

Should I retry Vertex AI "429 RESOURCE_EXHAUSTED"?

Yes. The official docs treat this error as retryable.

Which other AI APIs return HTTP 429?

Per their official error docs: Amazon Bedrock (429 ThrottlingException; 429 ModelNotReadyException), Anthropic API (429 rate_limit_error; 429 rate_limit_error (enforced_spend_limit_reached)), Azure OpenAI (429 Too Many Requests (Rate limit is exceeded); 429 Too Many Requests (System is experiencing high demand); 429 Too Many Requests (temporary rate limit adjustment); 429 Too Many Requests (token budget exceeded by request parameters)), Cohere API (429 Too Many Requests), DeepSeek API (429 - Rate Limit Reached), Gemini API (429 rate_limit_exceeded; 429 quota_exceeded; 429 too_many_requests; 429 RESOURCE_EXHAUSTED), Groq API (429 Too Many Requests), Mistral API (429 Too many requests), OpenAI API (429 credit_balance_exhausted; 429 Rate limit reached for requests; 429 rate_limit_error slow_down; 429 organization_spend_limit_exceeded; 429 project_spend_limit_exceeded; 429 organization_usage_limit_exceeded), OpenRouter (429 rate_limit_exceeded), xAI API (429 Too Many Requests).

Sources

Last verified against 3 sources: Vertex AI's official docs and official SDK repositories.

Newsletter

Know when the APIs change

One email per week. New model releases, API changes, what broke, and how developers are working around it.