From 79ee78ece036a6a83ff998e7b7b7badea34b0038 Mon Sep 17 00:00:00 2001 From: Sameer Kankute Date: Wed, 15 Apr 2026 17:38:06 +0530 Subject: [PATCH] fix(router): wildcard-aware deployment lookup for order-based fallback Use get_model_list() instead of _get_all_deployments() so pattern-routed model groups (e.g. openai/* -> openai/gpt-4.1-mini) are included when computing the deployment order set for fallback logic. Made-with: Cursor --- litellm/router.py | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/litellm/router.py b/litellm/router.py index 9185e437a3a..7ef4b3d621c 100644 --- a/litellm/router.py +++ b/litellm/router.py @@ -5358,9 +5358,11 @@ class Router: _request_team_id: Optional[str] = ( kwargs.get("metadata", {}) or {} ).get("user_api_key_team_id") - all_deployments = self._get_all_deployments( + # Use wildcard-aware lookup so order-based fallback also works for model + # groups resolved via pattern routing (e.g. `openai/*` -> `openai/gpt-4.1-mini`). + all_deployments = self.get_model_list( model_name=original_model_group, team_id=_request_team_id - ) + ) or [] _order_set: set = { litellm.utils._get_deployment_order(d) for d in all_deployments