LiteLLM / LiteLLM
LiteLLM Embedding Failover Missing num_retries Parameter
Fix LiteLLM embedding router not retrying or failing over when embedding host is unreachable Includes evidence for LiteLLM troubleshooting demand.
- Category
- LiteLLM
- Error signature
aembedding() missing num_retries kwarg — no failover for embedding model groups- Quick fix
- Compare the failing environment with a known working setup, then change one configuration value at a time.
- Updated
What this error means
aembedding() missing num_retries kwarg — no failover for embedding model groups is a LiteLLM failure pattern reported for developers trying to fix litellm embedding router not retrying or failing over when embedding host is unreachable. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.
Why this happens
Bug report (2026-05-07) identifies aembedding() in router.py doesn’t set num_retries before calling async completion, causing zero retries and no failover for embedding model groups when a host is unreachable.
Common causes
- LiteLLM proxy users with multiple embedding deployments expect automatic failover when a host goes down. The aembedding() method skips num_retries, causing single-attempt failures with no fallback — breaking production RAG/embedding pipelines.
- Bug report (2026-05-07) identifies aembedding() in router.py doesn’t set num_retries before calling async completion, causing zero retries and no failover for embedding model groups when a host is unreachable.
Quick fixes
- Confirm the exact error signature matches
aembedding() missing num_retries kwarg — no failover for embedding model groups. - Check the LiteLLM account, local tool state, and provider configuration involved in the failing workflow.
- Compare the failing environment with a known working setup, then change one configuration value at a time.
Platform/tool-specific checks
- Verify the command, editor, extension, or API client that produced the error.
- Compare local settings with CI, deployment, or editor-level settings when the error appears in only one environment.
- Avoid deleting credentials, local model data, or project settings until the failing scope is clear.
Step-by-step troubleshooting
- Capture the exact error message and the command, editor action, or request that triggered it.
- Check whether the failure is account/auth, quota/rate, model/provider, local runtime, or deployment configuration.
- Review the source evidence below and compare it with your environment.
- Apply one change at a time and rerun the smallest failing action.
- Keep the working fix documented for the team or deployment environment.
How to prevent it
- Keep provider/tool configuration documented.
- Record non-secret diagnostics such as tool version, provider name, model name, and command path.
- Add a lightweight check before CI or production workflows depend on the tool.
Sources checked
Evidence note: Bug report (2026-05-07) identifies aembedding() in router.py doesn’t set num_retries before calling async completion, causing zero retries and no failover for embedding model groups when a host is unreachable.
Related errors
- LiteLLM embedding retry not working
- LiteLLM router embedding deployment failover
FAQ
What should I check first?
Start with the exact aembedding() missing num_retries kwarg — no failover for embedding model groups text and the smallest action that reproduces it.
Can I ignore this error?
No. Treat it as a failed LiteLLM workflow until the root cause is understood.
Is this guaranteed to have one fix?
No. The imported evidence supports the troubleshooting path above, but tool behavior can vary by account, plan, version, provider, and local configuration.
How do I know the fix worked?
Rerun the same command, editor action, or request. The fix is working when that action completes without aembedding() missing num_retries kwarg — no failover for embedding model groups.