NousResearch/hermes-agent
Cron jobs lacking provider fallback on credential or rate-limit errors
Cluster 46511 · cron. Data as of
Nothing open on GitHub. Fix attempted, not merged.
The short answer
0open issues
0open PRs
3items grouped
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- No fix has been merged to main. 2 PRs closed without merging; see the attempts below.
- Tracker
- The maintainers' tracker marks this
unresolved. That is separate from the fix event. - Still open
- Nothing open on GitHub.
Next step: read the attempts below. Your case may extend or revive that work.
Pick up a Lab taskThe three members all concern cron jobs not falling back to another provider when credentials are exhausted or OAuth token refresh returns a 429/rate-limit error. Two are fix-style changes (one referencing #46511) and one is an issue report; their titles do not show the current status of any of them.
Open issues0
Open PRs0
2 PRs closed without merging
From the close comments: done elsewhere 1 · superseded by another PR 1
Closed issues · 1
- Closed#46511Cron jobs don't fallback when credential pool is exhausted (OAuth providers)
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
- Subsystem
- cron
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging