Capping auth refresh loops to enable fallback
Cluster 26080 · agent. Data as of
Nothing open on GitHub. Fix merged in #53919 on 28 Jun 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 #53919. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #53919. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These issues and PRs address a scenario where repeated credential refresh attempts on persistent 401/403 errors loop indefinitely, preventing fallback providers from activating. The work involves adding a cap on consecutive refresh attempts for the same credential entry so the fallback path can be reached.
Open issues0
Open PRs0
Fixes on record
-
#53919 fix(agent): cap same-entry credential refreshes so fallback can activate (#26080)
files:
agent/agent_runtime_helpers.py,agent/conversation_loop.py,tests/run_agent/test_run_agent.py
2 PRs closed without merging
From the close comments: merged via another change 1 · other 1
Closed issues · 1
- Closed#26080Credential pool refresh loop prevents fallback activation on persistent 401s
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
- Subsystem
- agent
- Merged PRs
- #53919
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 28 Jun 2026