6 views
-/https://github.com/berriai/litellm/issues/29808
GitHub · issue

#29808 [Bug]: MidStreamFallbackError is not being retried - vertexAI

  • State: open
  • Author: @powellnorma
  • Labels: bug, proxy, llm translation

### Check for existing issues

- [x] I have searched the existing issues and checked that my issue is not a duplicate.

### What happened?

A completion fails with ``` Message: litellm.MidStreamFallbackError: litellm.RateLimitError: litellm.RateLimitError: vertex_ai_betaException - b'{\n "error": {\n "code": 429,\n "message": "Resource exhausted. Please try again later. Please refer to https://cloud.google.com/vertex-ai/generative-ai/docs/error-code-429 for more details.",\n "status": "RESOURCE_EXHAUSTED"\n }\n}\n'No fallback model group found for original model_group=gemini-flash. Fallbacks=[]. Received Model Group=gemini-flash Available Model Group F... (litellm_truncated skipped 69 chars. Truncation is a DB storage safeguard. [..] ```

And it says in litellm UI: ``` Retries: None ```

However, in my litellm config I have: ``` router_settings: num_retries: 3 # retry each model group before falling back retry_after: 2 # seconds between retries ```

So I don't understand why it doesn't seem to do a retry?

### Steps to Reproduce

1. Use vertex gemini flash 3.5 2. Use it and wait for a 429 to appear 3. Look in the LitellmUI logs

### Relevant log output

```s…

GitHub resolver

Import GitHub neighbors on demand. Results are saved as system ingests.

Refresh page
vote history (2 events)
#0 of 0 · 31d18h18m46s ago — entered · #import:https:::github.com:berriai:litellm post #2639
The left requires diagnosing and correcting behavior across provider-specific error classification, streaming control flow, retry policy, and fallback integration, with regression coverage and operational risk. The right is informational and requires no product implementation.
#0 of 0 · 31d18h5m44s ago — current · #import:https:::github.com:berriai:litellm post #2866
The left issue is harder because it involves cross-worker database connection management, resource exhaustion, failure isolation, and deployment-level testing. The right issue is more localized to retry classification and control flow.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search