Nothing open on GitHub. Fix merged in #114726 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 #114726. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #114726. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These issues and PRs address a bug where long-lived cron processes silently skip all jobs due to stale or incorrectly handled imports of a shared constant (FIRE_CLAIM_SKEW_SECONDS). The fixes target the import resolution path to prevent module skew in cached processes.
Open issues0
Open PRs0
Fixes on record
-
#114726 fix(cron): a stale long-lived process no longer skips every job after an update (#114672, salvage #114675 #114692)
files:
contributors/emails/[redacted:email],cron/constants.py,cron/jobs.py,cron/occurrences.py,tests/cron/test_upgrade_module_skew.py
2 PRs closed without merging
From the close comments: merged via another change 2
Closed issues · 1
- Closed#114672[Bug] Stale long-lived process silently skips EVERY cron job: occurrences.py lazy-imports FIRE_CLAIM_SKEW_SECONDS from a cached old cron.jobs
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.83: 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
- #114726
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 18 Sep 2026