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
{{ message }}
Repository navigation
AI_RetryError: Failed after 4 attempts. Last error: Too Many Requests #2398
@andreluisos can you confirm this is still happening? I recall seeing something similar, but it was a while ago, and nothing since the (subsequent) latest update.
I now (v1.0.126) experience OC (apparently) spamming X.ai to the point where I see the red error message "Too many requests..."
Trying to divine what is happening from the logs is either neigh impossible... or I'm holding the wrong chicken and standing on the wrong leg - @rekram1-node any hints on where in the logs we can find what is happening?
@taqtiqa-mark what kind of logs are you looking for exactly? when you get 429s we continue to retry but with a backoff that respects the retry-after ratelimiting headers
The retry message you see is taken directly from the response from the server, or it should be
@taqtiqa-mark what kind of logs are you looking for exactly?
Ideally the full transcript of the API (pre-encryption/HTTPS) messages sent/received.
There is no way my message submissions triggered a rate limit violation, 10-20 messages tops across a couple of new sessions.
I also have a sneeking suspicion about what happens when OC chokes on the the XML parsing (mentioned in other issues), so it'd be nice to see the logs of that too.
In the spirit of calling out excellent engineering and design....
I've found that the Pi Coding Agent is more robust and, for me has none of the issues that I've encountered in OC, or has an elegant way to resolve them.... I'm dropping out of OC issues:
Activity
github-actions commentedon Sep 3, 2025
This issue might be a duplicate of existing issues. Please check:
rate_limit_exceeded#2244: Rate limiting issue with "rate_limit_exceeded" - similar retry/rate limiting symptomsFeel free to ignore if none of these address your specific case.
rekram1-node commentedon Sep 3, 2025
What provider are you using?
andreluisos commentedon Sep 3, 2025
Copilot and claude.
Nevermind... Only copilot is having the issue. Probaly provider issue.
rekram1-node commentedon Sep 3, 2025
You may be getting rate limited? 2 things:
rekram1-node commentedon Sep 3, 2025
we can also try looking at your logs
thoroc commentedon Sep 17, 2025
@andreluisos can you confirm this is still happening? I recall seeing something similar, but it was a while ago, and nothing since the (subsequent) latest update.
taqtiqa-mark commentedon Dec 2, 2025
I now (
v1.0.126) experience OC (apparently) spamming X.ai to the point where I see the red error message "Too many requests..."Trying to divine what is happening from the logs is either neigh impossible... or I'm holding the wrong chicken and standing on the wrong leg - @rekram1-node any hints on where in the logs we can find what is happening?
rekram1-node commentedon Dec 2, 2025
@taqtiqa-mark what kind of logs are you looking for exactly? when you get 429s we continue to retry but with a backoff that respects the retry-after ratelimiting headers
The retry message you see is taken directly from the response from the server, or it should be
taqtiqa-mark commentedon Dec 2, 2025
Ideally the full transcript of the API (pre-encryption/HTTPS) messages sent/received.
There is no way my message submissions triggered a rate limit violation, 10-20 messages tops across a couple of new sessions.
I also have a sneeking suspicion about what happens when OC chokes on the the XML parsing (mentioned in other issues), so it'd be nice to see the logs of that too.
taqtiqa-mark commentedon Dec 2, 2025
@rekram1-node progress is probably blocked by issue #4999 ?
taqtiqa-mark commentedon Feb 6, 2026
In the spirit of calling out excellent engineering and design....
I've found that the Pi Coding Agent is more robust and, for me has none of the issues that I've encountered in OC, or has an elegant way to resolve them.... I'm dropping out of OC issues:
github-actions commentedon Apr 7, 2026
To stay organized issues are automatically closed after 90 days of no activity. If the issue is still relevant please open a new one.