Credential pool 429 cooldown duration and configurability
NousResearch/hermes-agent · cluster 13619 · agent
Data as of
2 open items. Fix merged in #78380. Check it covers your case.
The short answer
- Known?
- Yes. 8 related items grouped here, 2 issues already closed.
- Fix event
- A fix was merged to main in PR #78380. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
partially resolved, deciding PR #78380. That is separate from the fix event. - Still open
- 2 issues and 0 PRs.
Next step: read #78380, then check whether your report is one of the 2 still open.
Read #78380Pick up a Lab taskThese issues and PRs concern the default cooldown period applied to credentials after a 429/403 response, with proposals to reduce it from 1 hour to a shorter duration and to make the TTL configurable rather than hardcoded. A specific concern is raised about single-credential pools being left unusable for the full cooldown period with no fallback.
Open issues2
Open PRs0
Fixes on record
-
#78380 fix(credential-pool): short cooldown for sole credential on transient throttle
files:
agent/agent_runtime_helpers.py,agent/credential_pool.py,tests/agent/test_credential_pool_routing.py,tests/agent/test_credential_pool_sole_cooldown.py,tests/run_agent/test_codex_xai_oauth_recovery.py,tests/run_agent/test_run_agent.py
3 PRs closed without merging
From the close comments: superseded by another PR 2 · merged via another change 1
-
#18713 fix: reduce default 429 cooldown from 1 hour to 3 minutes · superseded by another PR →
#22060 -
#22060 fix: reduce default 429 cooldown from 1 hour to 3 minutes (supersedes #18713) · superseded by another PR →
#94220 -
#53042 fix(credential-pool): short cooldown for sole credential on transient throttle · merged via another change →
#78380,#53041
Closed issues · 2
How this cluster was grouped
-
Link evidence (
partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text. - Members outside that structural core may belong to a different underlying problem.
-
Pairwise link density
0.18: 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
- #78380
- Closed issues
- 2
- Attempts
- 3 PRs closed without merging
- Fix link checked
- 4 Aug 2026