●MODEL — Gemini 3.5 Flash reaches GA and now powers gemini-flash-latest●AGENT — Managed Agents enter public preview in the Gemini API, running in isolated Google-hosted Linux sandboxes●SEARCH — File Search adds multimodal search, embedding and searching images natively via gemini-embedding-2●WEBHOOK — Event-driven webhooks arrive for the Batch API and long-running operations, replacing polling●EMBED — gemini-embedding-2 is now generally available for production embeddings●DEPRECATION — Several image generation models shut down on August 17, so plan migrations now●MODEL — Gemini 3.5 Flash reaches GA and now powers gemini-flash-latest●AGENT — Managed Agents enter public preview in the Gemini API, running in isolated Google-hosted Linux sandboxes●SEARCH — File Search adds multimodal search, embedding and searching images natively via gemini-embedding-2●WEBHOOK — Event-driven webhooks arrive for the Batch API and long-running operations, replacing polling●EMBED — gemini-embedding-2 is now generally available for production embeddings●DEPRECATION — Several image generation models shut down on August 17, so plan migrations now

TAG

retry-design

1 articles

← Back to all tags

gemini-api¹ batch-api¹ idempotency¹ indie-dev¹ operations¹

◈ Gemini API/2026-07-04Advanced

Catching the Rows That Quietly Failed Overnight: A Per-Row Retry Ledger for the Gemini Batch API

A SUCCEEDED batch job is not the same as all-rows-succeeded. From running nightly batches as a solo developer, here is a per-row result ledger, a transient-vs-permanent failure classifier, selective retries, and a guard against retrying permanent failures forever, with a working SQLite state machine.