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
It would be nice instead if we can support a model client that auto-recovers from various host-related errors with a configurable logic such as retries.
Here is a good example of an apparently transient error:
Moreover, even for rate limit errors like below, it doesn't always retry, there is some inconsistency happening
openai.RateLimitError: Error code: 429 - {'error': {'code': '429', 'message': 'Rate limit is exceeded. Try again in 1 seconds.'}}
Why is this needed?
Currently, the implementation of the chat completion client for OpenAI fails to recover and crashes for a host of errors (except for retries that are rate-limit related where it auto-retries), however, a host of other errors randomly occur and that forces the applications built on top of the client to have their own logic for auto-recovery.
The text was updated successfully, but these errors were encountered:
Just encountered the rate limiting error again, I think it would be good to have a retry logic built into the client itself. it's a pain to always have to write the code around the client.
ekzhu
changed the title
Auto Recovery Logic for chat completion clients
Auto Recovery Logic for chat completion clients on different types of server errors
Feb 18, 2025
What feature would you like to be added?
It would be nice instead if we can support a model client that auto-recovers from various host-related errors with a configurable logic such as retries.
Here is a good example of an apparently transient error:
Moreover, even for rate limit errors like below, it doesn't always retry, there is some inconsistency happening
Why is this needed?
Currently, the implementation of the chat completion client for OpenAI fails to recover and crashes for a host of errors (except for retries that are rate-limit related where it auto-retries), however, a host of other errors randomly occur and that forces the applications built on top of the client to have their own logic for auto-recovery.
The text was updated successfully, but these errors were encountered: