Cron resume behavior for elapsed recurring slots
Cluster 113603. Data as of
Nothing open on GitHub. Fix merged in #114792 on 18 Sep 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 #114792. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #114792. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These issues and PRs concern how cron jobs handle recurring slots that became due while paused — specifically whether elapsed slots are kept, skipped, or silently dropped on resume. Related behavior around error-status jobs missing execution rows is also mentioned.
Open issues0
Open PRs0
Fixes on record
-
#114792 fix(cron): resume keeps a recurring slot that elapsed while paused due instead of skipping it silently (#113603, salvage #114296)
files:
cron/jobs.py,tests/cron/test_jobs.py,website/docs/developer-guide/cron-internals.md,website/docs/reference/cli-commands.md,website/docs/user-guide/features/cron.md
2 PRs closed without merging
From the close comments: merged via another change 1 · superseded by another PR 1
Closed issues · 1
- Closed#113603cron job with last_status=error skipped next occurrence silently (no execution row)
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
- #114792
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 18 Sep 2026