Cron one-shot job run_claim not cleared on dispatch issue
Cluster 86522 · cron. Data as of
Nothing open on GitHub. Fix merged in #88337 on 17 Aug 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 #88337. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #88337. That is separate from the fix event. - Still open
- Nothing open on GitHub.
A bug caused one-shot cron jobs that were skipped or encountered a dispatch error to retain their run_claim, silently delaying re-execution until the claim TTL expired. The correction ensures run_claim is cleared in error and dispatch-skip paths.
Open issues0
Open PRs0
Fixes on record
-
#88337 fix(cron): clear run_claim for one-shot jobs on dispatch failure (salvage #87591)
files:
cron/jobs.py,cron/scheduler.py,tests/cron/test_oneshot_dispatch_failure_run_claim.py
2 PRs closed without merging
From the close comments: done elsewhere 1 · merged via another change 1
Closed issues · 1
- Closed#86522cron: one-shot job stamped with run_claim but skipped/failed at dispatch is silently delayed up to claim TTL (default 30 min)
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
- #88337
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 17 Aug 2026