Gemini 2.5 Flash Lite Batch API Error 429

Gemini API
1

Hi there,

I’m getting the following error when using Gemini 2.5 Flash Lite Batch API with a tier 3 paid account:

ERROR: 429 RESOURCE_EXHAUSTED. {‘error’: {‘code’: 429, ‘message’: ‘You exceeded your current quota, please check your plan and billing details. For more information on this error, head to: https://ai.google.dev/gemini-api/docs/rate-limits. To monitor your current usage, head to: https://ai.dev/rate-limit. ‘, ‘status’: ‘RESOURCE_EXHAUSTED’, ‘details’: [{’@type’: ‘type.googleapis.com/google.rpc.Help’, ‘links’: [{‘description’: ‘Learn more about Gemini API quotas’, ‘url’: ‘https://ai.google.dev/gemini-api/docs/rate-limits’}]}]}}

This has been going on for a few days. Even though I’m far below the 1 billion enqueued token limit, and I’m far below the 100 max bath jobs limit, its still giving me this error. It allows me to have 10 jobs max instead of 100 jobs.

2

anybody?? this is still occurring

3

Batch jobs are processed on a “best-effort” basis. If you are targeting a specific region that is currently under heavy load, the API will return a 429 to prevent further enqueuing, even if your global quota is open. And While Tier 3 allows 100 jobs, certain projects are occasionally limited to 10 concurrent jobs by an automated safety filter if the system detects a high “failure rate” or “burst pattern” in previous submissions.

You may try the following to see if they address your issue - 1) Check your region, ry switching your location (e.g., from us-central1 to europe-west1) to see if the 10-job cap persists. 2) Check if there is a “Limit” explicitly set to 10 for your specific project ID. and 3) You may implement Exponential Backoff. Even for Batch enqueuing, the API requires a retry strategy. If you are hitting the 10-job wall, wait 60 seconds before attempting to enqueue the 11th.

4

Thanks for the reply Jun. Changing the region fixed it. I’m now able to submit up to the 100 batch job limit.