Nothing open on GitHub. Fix merged in #111398 on 15 Sep 2026. Check it covers your case.
The short answer
0open issues
0open PRs
3items grouped
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #111398. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #111398. That is separate from the fix event. - Still open
- Nothing open on GitHub.
A cron job that removes itself during execution loses that run's output, logged as 'Fire claim ownership lost; stale result was discarded'. Members cover the bug report and associated fix attempts.
Open issues0
Open PRs0
Fixes on record
-
#111398 fix(cron): a job that removes itself during its run still delivers that run's output (#111039, salvage #111044)
files:
cron/jobs.py,cron/scheduler.py,tests/cron/test_script_claim_heartbeat.py,website/docs/user-guide/features/cron.md
1 PR closed without merging
From the close comments: won't fix / by design 1
-
#111044 fix(cron): deliver completed self-removing runs · won't fix / by design →
#111039
Closed issues · 1
- Closed#111039cron: a job that removes itself during its run loses that run's delivery ("Fire claim ownership lost; stale result was discarded")
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
- #111398
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 15 Sep 2026