Nothing open on GitHub. Fix merged in #132437 on 3 Oct 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 #132437. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #132437. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items address a bug where the stale in-flight sweep incorrectly releases healthy direct cron runs, causing them to run twice or lose liveness and registration ownership. The work involves preserving direct-run state during sweep operations.
Open issues0
Open PRs0
Fixes on record
-
#132437 Long manual cron runs are no longer swept as stale and run twice (salvage #132236)
files:
contributors/emails/[redacted:email],cron/scheduler.py,tests/cron/test_registration_ownership.py,tools/cronjob_tools.py
1 PR closed without merging
From the close comments: done elsewhere 1
-
#132236 fix(cron): preserve direct-run liveness and registration ownership · done elsewhere →
d6997d3,677e454,#132437
Closed issues · 1
- Closed#132223[Bug]: stale in-flight sweep releases healthy direct cron runs
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
- Merged PRs
- #132437
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 3 Oct 2026