Cron off-tick fire drops future scheduled slot
Cluster 110412 · cron. Data as of
1 open item. Fix merged in #111401 on 15 Sep 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 #111401. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #111401. That is separate from the fix event. - Still open
- 0 issues and 1 PR.
These items address a bug where a cron trigger firing outside its expected tick can incorrectly claim a future occurrence's identity, causing that scheduled slot to be silently skipped. The group includes the bug report and related fix attempts.
Open issues0
Open PRs1
- PR#110419fix(cron): stop off-tick fires from dropping future slots
Fixes on record
-
#111401 fix(cron): an off-tick fire no longer drops the next scheduled slot (#110412, salvage #106970 #110419)
files:
contributors/emails/[redacted:email],cron/jobs.py,cron/occurrences.py,cron/scheduler_provider.py,tests/cron/test_claim_job_for_fire.py,tests/cron/test_scheduled_occurrence.py,website/docs/developer-guide/cron-internals.md
Closed issues · 1
- Closed#110412Cron: an off-tick fire can claim a future occurrence's identity, silently dropping that slot forever
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
- #111401
- Closed issues
- 1
- Attempts
- 0 PRs closed without merging
- Fix link checked
- 15 Sep 2026