Cron Slack thread origin fixes for near one-shots
Cluster 117357. Data as of
Nothing open on GitHub. Fix merged in #117620 on 20 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 #117620. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #117620. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items address bugs where near one-shot or expired cron schedules incorrectly handled Slack reply-in-thread origins, causing reminders to deliver outside the intended thread context.
Open issues0
Open PRs0
Fixes on record
-
#117620 fix(cron): near one-shot Slack reminders deliver into the thread they were asked in; expired run_at fails closed (#117306, #117357, salvage #117343)
files:
tests/cron/test_cron_origin_synthetic_thread.py,tools/cronjob_job_args.py,tools/cronjob_tools.py
1 PR closed without merging
From the close comments: merged via another change 1
-
#117343 fix(cron): keep the Slack reply-in-thread origin for near one-shots · merged via another change →
5536004,#117620
Closed issues · 1
- Closed#117357fix(cron): expired one-shot schedules can incorrectly retain synthetic Slack thread origins
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
- #117620
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 20 Sep 2026