Rate-limit cooldown missing from fallback notices
Cluster 104120. Data as of
Nothing open on GitHub. Fix merged in #104967 on 7 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 #104967. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #104967. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items concern a bug where fallback notices omit the cooldown expiry time that the process has already calculated. The work involves surfacing that computed cooldown information in the notice shown to users.
Open issues0
Open PRs0
Fixes on record
-
#104967 fix: fallback notices show actual cooldown eligibility (#104120)
files:
agent/chat_completion_helpers.py,agent/fallback_cooldown.py,evals/provider_fallback/probe_104120.py,tests/run_agent/test_provider_fallback.py,website/docs/user-guide/features/fallback-providers.md
1 PR closed without merging
From the close comments: merged via another change 1
-
#104130 fix(agent): surface armed rate-limit cooldown in fallback notice (#104120) · merged via another change →
61d690a,#104967
Closed issues · 1
- Closed#104120Fallback notice omits the cooldown expiry the process already computed
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
- #104967
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 7 Sep 2026