Nothing open on GitHub. Fix merged in #114807 on 18 Sep 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 #114807. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
unresolved. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These members address the problem of cron job failures triggering repeated alerts on every run, and explore approaches to alert once per incident with a cooldown reminder rather than continuously.
Open issues0
Open PRs0
Fixes on record
-
#114807 fix(cron): a failing job alerts once per incident, then reminds on a cooldown (#113665, salvage #113685)
files:
contributors/emails/[redacted:email],cron/incidents.py,cron/scheduler.py,hermes_cli/config_defaults.py,tests/cron/test_cron_incidents.py,website/docs/user-guide/features/cron.md
1 PR closed without merging
From the close comments: done elsewhere 1
-
#113686 fix(cron): suppress repeated failure alerts · done elsewhere →
#114807,#113685,#113665
Closed issues · 1
- Closed#113684cron: a failing job re-alerts on every run, so operators mute failures entirely
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
- #114807
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 18 Sep 2026