8 views
-/https://github.com/berriai/litellm/issues/27473
GitHub · issue

#27473 [Bug]: v1.83.14 auto_router/complexity_router in litellm_params throws "Unmapped LLM provider" 400 error

  • State: open
  • Author: @abdulrahman-mpt
  • Labels: bug, proxy

### Check for existing issues

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

### What happened?

When configuring the LiteLLM proxy with `model: auto_router/complexity_router` inside a model's `litellm_params`, every request returns a 400 BadRequestError:

`litellm.BadRequestError: Unmapped LLM provider for this endpoint. You passed model=complexity_router, custom_llm_provider=auto_router`

When a fallback is configured, the fallback also fails because the router exposes the pre-alias model name (e.g. claude-sonnet-4-6) in the fallback lookup instead of the resolved group name (internal-ai), so no fallback entry matches: `No fallback model group found for original model_group=claude-sonnet-4-6. Fallbacks=[{'internal-ai': ['internal-haiku']}]. Available Model Group Fallbacks=None`

### Steps to Reproduce

1. Define two backend models in model_list (e.g. internal-haiku, internal-sonnet).

2. Define a router model that uses auto_router/complexity_router: ` - model_name: internal-ai litellm_params: model: auto_router/complexity_router complexity_router_config: tiers: SIMPLE: internal…

GitHub resolver

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

Refresh page
vote history (1 events)
#0 of 0 · 31d18h30m26s ago — entered · #import:https:::github.com:berriai:litellm post #2350
The left requires tracing and correcting cross-cutting routing, alias resolution, provider dispatch, and fallback behavior, with broader compatibility and regression risk. The right is a localized request-transformation fix with a comparatively narrow test surface.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search