Cron job results lost when fire-claim heartbeat missed
Cluster 113357. Data as of
Nothing open on GitHub. Fix merged in #114837 on 18 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 #114837. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #114837. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items address a bug where long-running cron jobs lose their completed status or result when the fire-claim heartbeat is missed or ownership lapses. The fixes aim to preserve completed job outcomes despite claim loss.
Open issues0
Open PRs0
Fixes on record
-
#114837 fix(cron): a completed run keeps its result when a fire-claim heartbeat sample misses (#113357, #105861, salvage #113364)
files:
cron/scheduler.py,tests/cron/test_fire_claim_lost_after_delivery.py,website/docs/developer-guide/cron-internals.md
1 PR closed without merging
From the close comments: merged via another change 1
-
#113364 fix(cron): preserve completed jobs after claim loss · merged via another change →
eafed27,132a181,#114837,#105861
Closed issues · 1
- Closed#113357Cron: long-running jobs (>60s) falsely marked 'Interrupted by shutdown' (fire-claim ownership lost)
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
- #114837
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 18 Sep 2026