One-shot cron job stuck or lost edge cases
Cluster 73973 · cron. Data as of
Nothing open on GitHub. Fix merged in #74134 on 29 Jul 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 #74134. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #74134. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These issues and fixes address scenarios where one-shot cron jobs can become permanently stuck or silently lost, particularly around claim_dispatch timing, scheduler restarts, unconfirmed dispatches, and unhandled exceptions.
Open issues0
Open PRs0
Fixes on record
-
#74134 fix(cron): record failure for BaseException escapes; diagnostic on wedged one-shot removal
files:
cron/jobs.py,cron/scheduler.py,tests/cron/test_jobs.py,tests/cron/test_run_one_job.py
2 PRs closed without merging
From the close comments: done elsewhere 2
Closed issues · 1
- Closed#73973One-shot cron jobs can get permanently stuck when claim_dispatch() increments completed before execution completes
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
- Subsystem
- cron
- Merged PRs
- #74134
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 29 Jul 2026