Cron escaped-run failures missing failure nudge alerts
Cluster 88655 · cron. Data as of
Nothing open on GitHub. Fix merged in #91836 on 21 Aug 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 #91836. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #91836. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These issues and PRs concern a gap where cron job failures at the scheduler level bypass the failure_nudge alerting mechanism, potentially leaving failures undetected. A fix is proposed to ensure escaped-run failures also trigger nudge review notifications.
Open issues0
Open PRs0
Fixes on record
-
#91836 fix(cron): nudge review of escaped-run failures too
files:
cron/scheduler.py,tests/cron/test_run_one_job.py,website/docs/user-guide/features/cron.md
1 PR closed without merging
From the close comments: merged via another change 1
-
#90686 fix(cron): nudge review of escaped-run failures too · merged via another change →
#91836,#88493
Closed issues · 1
- Closed#88655Scheduler-level cron processing errors bypass failure_nudge alerting — jobs can die silently for hours
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
- #91836
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 21 Aug 2026