NousResearch/hermes-agent
Recurring cron trigger_job blocked by stale-schedule guard
Cluster 94010. Data as of
Nothing open on GitHub. Fix merged in #96446 on 27 Aug 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 #96446. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #96446. That is separate from the fix event. - Still open
- Nothing open on GitHub.
A bug where trigger_job() silently does nothing for recurring cron jobs due to a stale-schedule guard introduced in #93049, along with multiple attempted fixes to preserve manual fire-now intent against that guard.
Open issues0
Open PRs0
Fixes on record
-
#96446 fix(cron): preserve recurring manual run intent against the stale-schedule guard (salvage of #94033)
files:
cron/jobs.py,tests/cron/test_due_stale_cron_edit.py
2 PRs closed without merging
From the close comments: duplicate 1 · merged via another change 1
Closed issues · 1
- Closed#94010[Bug]: trigger_job() is a silent no-op for every recurring cron job since the #93049 stale-schedule guard
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
- #96446
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 27 Aug 2026