Nothing open on GitHub. Fix merged in #129748 on 1 Oct 2026. Check it covers your case.
The short answer
- Known?
- Yes. 4 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #129748. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #129748. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items address cases where cron worker failures, lost runs, and stale claims are not properly surfaced or recorded. The work focuses on improving diagnostics, error reporting, and state management around cron worker lifecycle issues.
Open issues0
Open PRs0
Fixes on record
-
#129748 fix(cron): surface acknowledged worker failures and release stale claims
files:
cron/executions.py,cron/scheduler.py,cron/scheduler_worker_failure.py,tests/cron/test_restart_safe_worker.py,tests/cron/test_restart_safe_worker_death_evidence.py
2 PRs closed without merging
From the close comments: merged via another change 1 · superseded by another PR 1
Closed issues · 1
- Closed#129254Cron agent-mode worker dies silently before agent starts (execution stuck, no error, no delivery)
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
- #129748
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 1 Oct 2026