NousResearch/hermes-agent
Cron dispatch failures not creating incidents or alerts
Cluster 123401. Data as of
Nothing open on GitHub. Fix merged in #124013 on 26 Sep 2026. Check it covers your case.
The short answer
0open issues
0open PRs
4items grouped
- Known?
- Yes. 4 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #124013. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #124013. That is separate from the fix event. - Still open
- Nothing open on GitHub.
A bug was identified where cron job dispatch failures to external workers produced no incident record and no failure notification. Related fixes address surfacing these failures through the incident and alerting path.
Open issues0
Open PRs0
Fixes on record
-
#124013 fix(cron): alert on restart-safe worker dispatch failures (salvage #123432)
files:
cron/scheduler.py,tests/cron/test_restart_safe_worker.py
2 PRs closed without merging
From the close comments: done elsewhere 2
Closed issues · 1
- Closed#123401[BUG] Cron dispatch failures create no incident and send no failure notification
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
- #124013
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 26 Sep 2026