Fix misclassified 429 upstream errors draining API keys
Cluster 117111. Data as of
Nothing open on GitHub. Fix merged in #117575 on 20 Sep 2026. Check it covers your case.
The short answer
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #117575. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #117575. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items address a bug where upstream-unavailable 429 responses from CommandCode are incorrectly treated as credential rate limit errors, causing healthy API keys to be unnecessarily exhausted. The work involves correcting this misclassification so API keys remain healthy during upstream outages.
Open issues0
Open PRs0
Fixes on record
-
#117575 fix(agent): CommandCode upstream-unavailable 429 keeps the API key healthy (#117111, salvage #117117)
files:
agent/error_classifier.py,tests/agent/test_error_classifier.py
1 PR closed without merging
From the close comments: merged via another change 1
-
#117117 fix(agent): keep CommandCode keys healthy during upstream outages · merged via another change →
30d14a3,#117575
Closed issues · 1
- Closed#117111[Bug]: CommandCode upstream-unavailable 429 is misclassified as credential rate limit and exhausts a healthy API key
How this cluster was grouped
-
Link evidence (
structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference. -
Pairwise link density
0.67: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means every pair is linked.
Pick up a Lab task
Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.
Open the LabAt a glance
- Merged PRs
- #117575
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 20 Sep 2026