From 6b182ae63e91ad8435f42fae558740d1cd88ceb5 Mon Sep 17 00:00:00 2001 From: Arthur Darcet Date: Fri, 3 Apr 2026 15:24:09 +0200 Subject: [PATCH] Remove Mistral specific mapping for 429 errors When Mistral replies with a 503 error and message 'service tier capacity exceeded', it means the backend was at capacity, not that the user reached their rate limit and the error should not be converted to RateLimitError --- litellm/litellm_core_utils/exception_mapping_utils.py | 6 ------ 1 file changed, 6 deletions(-) diff --git a/litellm/litellm_core_utils/exception_mapping_utils.py b/litellm/litellm_core_utils/exception_mapping_utils.py index bc54786420a..f0e7fb62ca9 100644 --- a/litellm/litellm_core_utils/exception_mapping_utils.py +++ b/litellm/litellm_core_utils/exception_mapping_utils.py @@ -56,12 +56,6 @@ class ExceptionCheckers: if re.search(r"rate[\s_\-]*limit", _error_str_lower): return True - ####################################### - # Mistral API returns this error string - ######################################### - if "service tier capacity exceeded" in _error_str_lower: - return True - return False @staticmethod