LiteLLM / LiteLLM

LiteLLM proxy team-scoped model fallback fails with public-to-internal name mismatch

Fix LiteLLM proxy fallback not triggering for team-scoped BYOK models due to public vs internal model name mismatch in Router.async_function_with_fallbacks Includes evidence for LiteLLM troubleshooting demand.

Source-backed Last updated May 22, 2026 1 source Needs local verification

Category: LiteLLM
Error signature: No fallback model group found for original model_group=primary. Available Model Group Fallbacks=None
Quick fix: Compare the failing environment with a known working setup, then change one configuration value at a time.
Updated: May 22, 2026
Verification status: Source-backed
Evidence: 1 public source URL

Before you change production

This page includes public source URLs in the imported troubleshooting record. Compare those references with your version and environment before applying changes.

Reproduce the smallest failing action and save non-secret logs before changing configuration.
Check versions for LiteLLM, related SDKs, package managers, CI runners, and hosting providers.
Change one setting or dependency at a time, then rerun the same failing command or request.
Avoid destructive commands, credential rotation, billing changes, or security relaxations without a rollback plan.

What this error means

No fallback model group found for original model_group=primary. Available Model Group Fallbacks=None is a LiteLLM failure pattern reported for developers trying to fix litellm proxy fallback not triggering for team-scoped byok models due to public vs internal model name mismatch in router.async_function_with_fallbacks. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.

Why this happens

GitHub issue #28019 on BerriAI/litellm documents a routing bug: POST /fallback requires internal model names (model_name_team_uuid) but runtime requests use public names (e.g. gpt-4.1). The fallback lookup does direct string comparison before name resolution, so it never matches. Root cause identified in code (Router.async_function_with_fallbacks). Workaround available via model_aliases. Strong commercial value — directly impacts production proxy billing and failover reliability.

Common causes

GitHub issue #28019 on BerriAI/litellm documents a routing bug: POST /fallback requires internal model names (model_name_team_uuid) but runtime requests use public names (e.g. gpt-4.1). The fallback lookup does direct string comparison before name resolution, so it never matches. Root cause identified in code (Router.async_function_with_fallbacks). Workaround available via model_aliases. Strong commercial value — directly impacts production proxy billing and failover reliability.

Quick fixes

Confirm the exact error signature matches No fallback model group found for original model_group=primary. Available Model Group Fallbacks=None.
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.

Diagnostic flow for this page

Match No fallback model group found for original model_group=primary. Available Model Group Fallbacks=None exactly before applying the quick fix.
Compare the failing environment with LiteLLM versions, account scope, provider settings, and deployment context.
Check the listed common causes in order, starting with the cause that best matches your logs.
Use the evidence status below to decide whether to confirm against public sources or official documentation.
Apply one reversible change, rerun the smallest failing action, and keep rollback notes.

FAQ

What does No fallback model group found for original model_group=primary. Available Model Group Fallbacks=None mean in LiteLLM?

No fallback model group found for original model_group=primary. Available Model Group Fallbacks=None indicates the workflow described by "LiteLLM proxy team-scoped model fallback fails with public-to-internal name mismatch" failed in a LiteLLM context. Start by confirming the exact signature and the component that emitted it.

What should I check first for No fallback model group found for original model_group=primary. Available Model Group Fallbacks=None?

Check whether this cause matches your environment: GitHub issue #28019 on BerriAI/litellm documents a routing bug: POST /fallback requires internal model names (model_name_team_uuid) but runtime requests use public names (e.g. gpt-4.1). The fallback lookup does direct string comparison before name resolution, so it never matches. Root cause identified in code (Router.async_function_with_fallbacks). Workaround available via model_aliases. Strong commercial value — directly impacts production proxy billing and failover reliability.

Is the No fallback model group found for original model_group=primary. Available Model Group Fallbacks=None guidance source-backed?

The "LiteLLM proxy team-scoped model fallback fails with public-to-internal name mismatch" page is labeled source-backed. It has 1 public source URL from github.com, so use that evidence status when deciding how much additional verification you need.

When should I avoid the quick fix for No fallback model group found for original model_group=primary. Available Model Group Fallbacks=None?

For "LiteLLM proxy team-scoped model fallback fails with public-to-internal name mismatch", avoid applying "Compare the failing environment with a known working setup, then change one configuration value at a time." when the error text differs, the affected version or provider is different, or the change would touch credentials, billing, DNS, production deploy settings, or irreversible data.

What should I collect before debugging No fallback model group found for original model_group=primary. Available Model Group Fallbacks=None?

For "LiteLLM proxy team-scoped model fallback fails with public-to-internal name mismatch", collect the failing LiteLLM command or request, non-secret configuration, versions, timestamps, request IDs when available, and the smallest reproduction that still triggers the signature.