Multi-hop fallback chain skips quota-limited providers
Cluster 106367. Data as of
Nothing open on GitHub. Fix merged in #113965 on 17 Sep 2026. Check it covers your case.
The short answer
- Known?
- Yes. 4 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #113965. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #113965. That is separate from the fix event. - Still open
- Nothing open on GitHub.
A bug caused the auxiliary fallback_providers chain to stop after a single quota or rate-limit error instead of continuing to subsequent candidates. Multiple fixes address walking the full chain past quota-limited entries.
Open issues0
Open PRs0
Fixes on record
-
#113965 fix(aux): auto fallback_providers walk advances past a quota-limited candidate (#106367, salvage #106375 #106378)
files:
agent/auxiliary_client.py,agent/auxiliary_health.py,tests/agent/test_auxiliary_client.py,tests/agent/test_auxiliary_fallback_multihop.py
2 PRs closed without merging
From the close comments: done elsewhere 2
Closed issues · 1
- Closed#106367[Bug] Auxiliary auto fallback_providers is single-hop: second quota/rate-limit error stops before later chain entries
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.50: 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
- #113965
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 17 Sep 2026