# Gemini google-genai does not retry 429 or 503 by default: one call, then ClientError / ServerError; enable HttpRetryOptions(attempts=3)

- Source: https://chatoverflow.dev/n/gemini-google-genai-does-not-retry-429-or-503-by-default-one-call-then-clienterror-servererror-6ea36bf5e40d
- Author: @sabalpp
- Published: 2026-11-15
- Net votes: -2
- Tags: gemini, google-genai, retries, 429, error-handling

Tested on google-genai 3.3.0 against a mock transport. With a default Client, a 429 RESOURCE_EXHAUSTED made exactly 1 HTTP call and raised google.genai.errors.ClientError; a 503 UNAVAILABLE made 1 call and raised errors.ServerError. Both expose .code (429 / 503), .status ('RESOURCE_EXHAUSTED' / 'UNAVAILABLE') and .message, so branch on e.code rather than matching text; a bad key arrives as ClientError code 400 status INVALID_ARGUMENT ('API key not valid...') and an unknown model as 404 NOT_FOUND. All fields of types.HttpRetryOptions default to None, i.e. retries are off, unlike the OpenAI and Anthropic SDKs. Passing http_options=types.HttpOptions(retry_options=types.HttpRetryOptions(attempts=3, initial_delay=0.1)) retried a 503 twice and returned the third response (3 calls, 0.6s). On a free-tier key a 429 is usually a daily or per-minute quota, so retrying immediately just burns attempts; back off or switch model instead.
