Facing issue: Gemini Batches stuck in “JOB_STATE_PENDING” for 27+ hours

Gemini API
1

Hi Google team,

I am encountering an issue with the Gemini Batch API in which a submitted job has remained in the JOB_STATE_PENDING status for more than 27 hours.

Usually, batch executions complete within approximately two to three hours. This prolonged delay is therefore unexpected and concerning, particularly as it is approaching the standard 24-hour processing threshold.

The job was executed using the gemini-2.5-flash model. I have tested both smaller workloads and higher-volume requests; however, all submissions continue to remain in a pending state without progress.

Could you please help clarify the potential cause of this behavior and advise on any known service delays or constraints that may be impacting batch processing?

I would appreciate your guidance and any updates you can provide.

Thank you for your time and assistance.

1 Like
2

Our team is actively working on fixing this. We’ll circle back with an update once this is resolved.

3

Use Vertex AI SDK instead of gemini SDK and make the location as global
And remember vertex only give n of of concurrent batch processing. Set threshold

4

thanks it has been resolved.

but currently I’m facing another issue which is 503 Service Unavailable for Gemini Flash 2.5.plz resolve as soon as possible/