This is fairly unusual, one of the batches has gone on for 17+ hours, I’m on tier 1 (should be tier 2 soon but the button isn’t available yet) and it wasn’t a problem before today. This is on gemini-2.5-flash so not sure if the model is the cause I have yet to test on gemini-3
Anyone else experience unusual times for the batch API?
I am on Tier 1 and am using Gemini 2.5 Pro, and I encountered almost the same issue.
My task submitted via the Batch API remained in a pending state for over 24 hours, even though it is usually completed in less than 10 minutes.
I retried the task several times, but the behavior did not change.
However, the same task completed successfully and without issues when using the synchronous API.
This suggests that the issue may be specific to the Batch API.
Yep, I think it’s only the Batch API with this issue I have tested with several of the models to see if it’s model specific, gemini-3-flash-preview and gemini-2.0-flash also seem to have the same problems.
Status on google systems looks all good but there is clearly an issue, SLA for batches are usually processed within 24 hours, only thing i can think of is a zombie failure where it’s not reporting it back and failing silently
Hi @chanduriv it seems like there is an ongoing issue again with the Batch API. I have the following that have been pending for around 6 hours at BATCH_STATE_PENDING
Same here. Submitted a gemini-3-flash-preview batch coming up on 26 hours ago that is still in pending status. We heavily use cached content as well, deleting them upon batch completion. So these batches not completing is racking up significant cache storage costs for us as well