Cron run completion requires persisted assistant message
Cluster 93820. Data as of
Nothing open on GitHub. Fix merged in #96447 on 27 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 #96447. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #96447. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These issues and fixes address a bug where cron runs were marked complete without a persisted final assistant message, making silent failures invisible in run history. The fix adds a verification step before a run can be booked as complete.
Open issues0
Open PRs0
Fixes on record
-
#96447 fix(cron): verify a persisted final assistant message before booking complete (salvage of #93829)
files:
cron/scheduler.py,tests/cron/test_scheduler_completion_verification.py
2 PRs closed without merging
From the close comments: merged via another change 1 · superseded by another PR 1
Closed issues · 1
- Closed#93820Cron runs marked complete without any persisted final assistant message (silent failures invisible in run history)
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
- #96447
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 27 Aug 2026