Google Vertex AI (generative AI) error
Vertex AI 429 Resource exhausted, please try again later: what it means and how to fix it
429 Resource exhausted, please try again later.Retry? YesLast verified 4 documented fixes1 source
What it means
The 429 message returned on the pay-as-you-go quota framework when no reserved capacity is available. Such requests are not counted against your SLA error rate.
Causes
- Shared pay-as-you-go capacity is not available to your request
- Project quota exceeded
- Sharp usage increase hitting acceleration limits
How to fix it
- Fix 1.
Use the global endpoint instead of a regional endpoint whenever possible.
- Fix 2.
Implement a retry strategy using truncated exponential backoff.
- Fix 3.
Submit a Quota Increase Request if your model uses quotas; on Standard pay-as-you-go, smooth traffic and reduce large spikes.
- Fix 4.
Subscribe to Provisioned Throughput for a more consistent level of service.
More Vertex AI errors
All 11 Vertex AI errors400 INVALID_ARGUMENT / FAILED_PRECONDITIONRetry? No401 UNAUTHENTICATEDRetry? No403 PERMISSION_DENIEDRetry? No404 NOT_FOUNDRetry? No429 RESOURCE_EXHAUSTEDRetry? Yes429 Too many requests. Exceeded the Provisioned ThroughputRetry? Not stated499 CANCELLEDRetry? Not stated500 UNKNOWN / INTERNALRetry? Yes
HTTP 429 at other providers
Compare 429 across providers429 ThrottlingExceptionRetry? YesAmazon Bedrock429 ModelNotReadyExceptionRetry? YesAmazon Bedrock429 rate_limit_errorRetry? YesAnthropic API429 rate_limit_error (enforced_spend_limit_reached)Retry? NoAnthropic API429 Too Many Requests (Rate limit is exceeded)Retry? YesAzure OpenAI429 Too Many Requests (System is experiencing high demand)Retry? YesAzure OpenAI429 Too Many Requests (temporary rate limit adjustment)Retry? YesAzure OpenAI429 Too Many Requests (token budget exceeded by request parameters)Retry? Not statedAzure OpenAI429 Too Many RequestsRetry? YesCohere API429 - Rate Limit ReachedRetry? Not statedDeepSeek API429 rate_limit_exceededRetry? YesGemini API429 quota_exceededRetry? YesGemini API
FAQ
What does the Vertex AI error "429 Resource exhausted, please try again later" mean?
The 429 message returned on the pay-as-you-go quota framework when no reserved capacity is available. Such requests are not counted against your SLA error rate.
How do I fix Vertex AI "429 Resource exhausted, please try again later"?
There are 4 documented fixes. Start with the first: Use the global endpoint instead of a regional endpoint whenever possible.
Should I retry Vertex AI "429 Resource exhausted, please try again later"?
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 1 source: 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.