Cron long deliveries starving heartbeat, recorded as errors
Cluster 108862 · cron. Data as of
Nothing open on GitHub. Fix merged in #109310 on 12 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 #109310. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
unresolved. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These members concern cron runs where a delivery taking over about 30 seconds appears to starve the run's fire-claim heartbeat, so delivered runs get recorded with an 'ownership lost' error status. One is an issue describing the problem and the other two appear to be fix proposals; the titles do not confirm any outcome.
Open issues0
Open PRs0
Fixes on record
-
#109310 fix(cron): long fenced deliveries no longer recorded as failed 'ownership lost' (#108341, #100401; salvage #106745)
files:
cron/jobs.py,tests/cron/test_claim_job_for_fire.py
1 PR closed without merging
From the close comments: done elsewhere 1
-
#109079 Fix cron heartbeat starvation during long deliveries · done elsewhere →
#108862,#100401,#109310
Closed issues · 1
- Closed#108862Cron: a delivery leg over 30s starves the run's own fire-claim heartbeat, booking delivered runs as failed
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
- #109310
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 12 Sep 2026