NousResearch/hermes-agent
Cron delivery retention race condition fixes
Cluster 104001 · cron. Data as of
1 open item. Fix merged in #104909 on 7 Sep 2026. Check it covers your case.
The short answer
0open issues
1open PR
3items grouped
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #104909. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #104909. That is separate from the fix event. - Still open
- 0 issues and 1 PR.
These issues and pull requests address a race condition where cron delivery retention logic could conflict with enqueue operations, potentially resurrecting already-delivered executions. The work focuses on serializing deduplication with terminal retention to prevent this.
Open issues0
Open PRs1
- PR#104002fix(cron): serialize delivery deduplication with terminal retention
Fixes on record
-
#104909 fix: delivered cron runs stay delivered during retention (#104001, salvage #104002)
files:
cron/delivery_queue.py,tests/cron/test_delivery_queue_retention_race.py
Closed issues · 1
- Closed#104001Cron delivery retention can race enqueue and resurrect an already delivered execution
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
- Merged PRs
- #104909
- Closed issues
- 1
- Attempts
- 0 PRs closed without merging
- Fix link checked
- 7 Sep 2026