anomalyco/opencode
1
0
Fork 0
mirror of https://github.com/anomalyco/opencode.git synced 2026-07-22 02:05:26 -04:00
Code Issues 5.9k Packages Projects Releases 19 Wiki Activity

Excessive retry backoff (~2 weeks) on "Quota Exceeded" with no mechanism to reset/force retry #9326

New Issue
Closed
opened 2026-02-16 18:12:11 -05:00 by yindo · 2 comments
yindo commented 2026-02-16 18:12:11 -05:00
Owner
Copy Link
Copy Source

Originally created by @morganrcu on GitHub (Feb 14, 2026).

Originally assigned to: @rekram1-node on GitHub.

Question

I encountered a Too Many Requests: quota exceeded error while using the claude-opus-4.6 model due to insufficient funds. The tool triggered a retry mechanism with an unreasonably long wait time (~2 weeks).

After replenishing my GitHub funds/credits, the tool remains stuck in this retry loop. I cannot find a way to manually force a retry or reset the timer without potentially losing my current context/session.

Steps to Reproduce:

Run a task using claude-opus-4.6.

Exhaust the API quota/funds to trigger a 429 Too Many Requests error.

Observe the retry timer.

Current Behavior:

The CLI displays:

Too Many Requests: quota exceeded [retrying in ~2 weeks attempt #1]
The application waits indefinitely (or for the displayed duration) and does not detect that funds have been restored.

Expected Behavior:

The retry backoff time should be reasonable (e.g., minutes, not weeks).

There should be a keybinding or command to force an immediate retry (e.g., r to retry) after the user has resolved the payment issue.

Screenshots:

Image

Environment:

Model: Claude Opus 4.6 (via GitHub Copilot)

OS: Linux
Originally created by @morganrcu on GitHub (Feb 14, 2026). Originally assigned to: @rekram1-node on GitHub. ### Question I encountered a Too Many Requests: quota exceeded error while using the claude-opus-4.6 model due to insufficient funds. The tool triggered a retry mechanism with an unreasonably long wait time (~2 weeks). After replenishing my GitHub funds/credits, the tool remains stuck in this retry loop. I cannot find a way to manually force a retry or reset the timer without potentially losing my current context/session. Steps to Reproduce: Run a task using claude-opus-4.6. Exhaust the API quota/funds to trigger a 429 Too Many Requests error. Observe the retry timer. Current Behavior: The CLI displays: Too Many Requests: quota exceeded [retrying in ~2 weeks attempt #1] The application waits indefinitely (or for the displayed duration) and does not detect that funds have been restored. Expected Behavior: The retry backoff time should be reasonable (e.g., minutes, not weeks). There should be a keybinding or command to force an immediate retry (e.g., r to retry) after the user has resolved the payment issue. Screenshots: <img width="1818" height="190" alt="Image" src="https://github.com/user-attachments/assets/91514eb3-a83f-4619-bedb-45109de2fd8d" /> Environment: Model: Claude Opus 4.6 (via GitHub Copilot) OS: Linux
yindo added the zen label 2026-02-16 18:12:11 -05:00
yindo closed this issue 2026-02-16 18:12:11 -05:00
yindo commented 2026-02-16 18:12:11 -05:00
Author
Owner
Copy Link
Copy Source

@github-actions[bot] commented on GitHub (Feb 14, 2026):

For keybind-related requests like this, please also check our pinned keybinds documentation: #4997

@github-actions[bot] commented on GitHub (Feb 14, 2026): For keybind-related requests like this, please also check our pinned keybinds documentation: #4997
yindo commented 2026-02-16 18:12:11 -05:00
Author
Owner
Copy Link
Copy Source

@morganrcu commented on GitHub (Feb 14, 2026):

I wait and problem was removed.... sorry for any inconvinience

@morganrcu commented on GitHub (Feb 14, 2026): I wait and problem was removed.... sorry for any inconvinience
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
acp
bad
bug
discussion
docs
documentation
enhancement
extension
good first issue
growth
help-wanted
mcp
model-problem
needs:compliance
nix
opentui
perf
pull-request
Mirrored from GitHub Pull Request
 tui
web
windows
zen
No Label zen
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#9326
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?