Classify Gemini API Errors by Status — Handling 429, SAFETY, and Token Limits in Production
Sort Gemini API failures along two axes — HTTP status and finish_reason — so you know instantly whether to wait or to fix. Covers the three distinct 429 limits, model-deprecation fallbacks, and how the exception hierarchy changes after moving to the google-genai SDK.
Don't Retry Every Gemini 429 — Telling Rate Limits Apart From Spend Cap Exhaustion
A 429 RESOURCE_EXHAUSTED can mean 'wait a second and it clears' or 'you're out of budget for the month.' Now that Project Spend Caps is generally available, the second case is real in production. Here's how to classify the two and build a retry layer plus a circuit breaker around them.
Gemini 2.5 Pro in Production: The Pitfalls Nobody Talks About
A practical guide to the production-specific problems with Gemini 2.5 Pro—rate limit architecture, Thinking mode cost control, long-context quality management, and response quality diagnostics—with complete code examples.
Gemini API Practical Troubleshooting Guide — Master 2.5 Pro Rate Limits, Timeouts & Errors
Systematically troubleshoot Gemini 2.5 Pro API errors: 429 rate limits, 504 timeouts, 400 validation errors, and Safety Filter blocks. Learn production-ready solutions with retry strategies, streaming optimization, and cost-saving techniques.