Cron no-agent script failure visibility bug fix
Cluster 118354. Data as of
Nothing open on GitHub. Fix merged in #127596 on 3 Oct 2026. Check it covers your case.
The short answer
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #127596. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #127596. That is separate from the fix event. - Still open
- Nothing open on GitHub.
A bug where a no-agent cron script failure is silently overwritten by the next successful run, causing the failure to disappear from history. The fix preserves a sticky last-failure stamp so past failures remain visible even after subsequent successes.
Open issues0
Open PRs0
Fixes on record
-
#127596 fix(cron): keep a sticky last_failure stamp so a healed no_agent script failure stays visible
files:
cron/jobs.py,hermes_cli/cron.py,tests/cron/test_last_failure_stamp.py
1 PR closed without merging
From the close comments: other 1
-
#118387 fix(cron): preserve no-agent script failure history · other →
#118354,#127596
Closed issues · 1
- Closed#118354[Bug]: no_agent cron script failure is erased by the next successful run - last_status and failure_streak self-heal, so a relapse is invisible
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
- Merged PRs
- #127596
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 3 Oct 2026