Cron jobs.json concurrent write clobbering fixes
Cluster 80624. Data as of
Nothing open on GitHub. Fix merged in #81000 on 7 Aug 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 #81000. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #81000. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These members address a bug where concurrent processes writing to jobs.json could overwrite or drop cron jobs created by other processes. Multiple fix attempts target preserving jobs written during unlocked saves and recovering sibling-process entries.
Open issues0
Open PRs0
Fixes on record
-
#81000 fix(cron): preserve concurrent creates when saving jobs.json (salvage of #80687 + #80703)
files:
cron/jobs.py,tests/cron/test_jobs_shrink_merge_80624.py
2 PRs closed without merging
From the close comments: superseded by another PR 2
Closed issues · 1
- Closed#80624no_agent script cron jobs disappear from jobs.json while gateway is running (CLI-created jobs clobbered by scheduler state)
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.50: 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
- #81000
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 7 Aug 2026