You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please define the error with http code 502 (bad gateway) separately from API Error.
Motivation, pitch
Over at openhands, we are using litellm SDK and have retries with tenacity on completion. We have encountered an issue:
litellm's APIError is a catch-all for various permanent errors (e.g. entity too large, Cloudflare blocks, etc), so we should not retry on it
but it includes 502, bad gateway, which is typically temporary, so we should retry on it.
Could you please separate and define another exception for 502?
It seems a good idea to me simply because one is temporary and others permanent. Normally no one wants to retry things that cannot succeed.
Note: litellm proxy itself can return quite a number of 502 errors, and they are clearly temporary. It's one of the most common temporary errors out there. 😅 Please help us catch them nicely, without the rest of API Error.
Twitter / LinkedIn details
No response
The text was updated successfully, but these errors were encountered:
The Feature
Please define the error with http code 502 (bad gateway) separately from API Error.
Motivation, pitch
Over at
openhands
, we are using litellm SDK and have retries with tenacity oncompletion
. We have encountered an issue:Could you please separate and define another exception for 502?
It seems a good idea to me simply because one is temporary and others permanent. Normally no one wants to retry things that cannot succeed.
Note: litellm proxy itself can return quite a number of 502 errors, and they are clearly temporary. It's one of the most common temporary errors out there. 😅 Please help us catch them nicely, without the rest of API Error.
Twitter / LinkedIn details
No response
The text was updated successfully, but these errors were encountered: