[Batch API Error] "Deadline expired before operation could complete" or "The operation was cancelled" for gemini-3-flash-preview

[ocean]

I am using gemini-3-flash-preview in batch API mode. The results are returning longer than normal, and most of the results in the jsonl file are as follows:

{“error”: {“message”: “Deadline expired before operation could complete.”, “code”: 4}, “key”: “20260126230149001856_24ba5bce_000000”}

{“error”: {“code”: 4, “message”: “Deadline expired before operation could complete.”}, “key”: “20260126230149001856_24ba5bce_000001”}

{“error”: {“message”: “The operation was cancelled.”, “code”: 1}, “key”: “20260126230149001856_24ba5bce_000041”}

…

This problem has lasted for about 12 hours now and is universal for 3 batch API tasks so far with very high error rates as following:

[Batch Gemini] - batches/autk717sgn1vgpjfp1akw1nxc1g2mn53mwv3 - State: BATCH_STATE_SUCCEEDED - Progress: 6/34 (failed: 28) - Elapsed: 8129s

[Batch Gemini] - batches/pz7a95taky17ifw6yxgw115em5ds047kn1c6 - State: BATCH_STATE_SUCCEEDED - Progress: 10/49 (failed: 39) - Elapsed: 4009s

[Yanning_Qiu]

My gemini-3-flash-preview existing batches are pending for very long and, some others even got 429 error, but I am far below the rate limit…

[Brant]

I had a batch stuck in pending for 36 hours or so, so I decided to cancel it. Then I tried to submit a new batch and now it says 429 error. No other batches are in queue. I checked. This error makes no sense…

@Yanning_Qiu Yes this happens to me as well. There was never any clarification or fix for it.