-
Notifications
You must be signed in to change notification settings - Fork 379
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug: Retrying inappropriate errors #556
Comments
Makes a lot of sense. Any ideas on the best way to differentiate? |
I think some 429 errors tell you when to try again - that would be great to consider as well |
Above is example from Anthropic - ideally other providers would follow similar conventions regarding error codes. 80/20 is likely to base retry strategy on error code and iterate from there. Can use exponential retry + jitter to attempt retry of rate limit, but tbh, I think that may be worse UX (in case of rate limit specifically) than just not retrying - rate limit issue with Roo is usually bc API key lacks capacity that Roo needs, or something is going wrong (like a massive tool call result or similar) that should not be retried. |
A rate limit error from Roo typically results from:
In either branch, we shouldn't retry - I would recommend only retrying for connection errors.
Example of the failure mode:
Originally posted by @veerababumanyam in #554
The text was updated successfully, but these errors were encountered: