Cron dispatch-failure notice credential/profile binding
Cluster 131585. Data as of
Nothing open on GitHub. Fix merged in #132446 on 3 Oct 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 #132446. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #132446. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items address a bug where cron crash or dispatch-failure notices use incorrect credentials or profile scope, particularly on multi-profile gateway setups. The work involves binding the correct profile's secret scope when sending these notices.
Open issues0
Open PRs0
Fixes on record
-
#132446 Cron crash notices use the firing profile's credentials (salvage #130431)
files:
contributors/emails/[email protected],cron/scheduler.py,tests/cron/test_restart_safe_worker.py
1 PR closed without merging
From the close comments: done elsewhere 1
-
#130431 fix(cron): bind the profile secret scope for the dispatch-failure notice · done elsewhere →
8d15ca4,c8815a5,#132446
Closed issues · 1
- Closed#131585[Bug]: Cron dispatch-failure notice still isn't delivered on multi-profile gateways (#123401 follow-up)
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
- #132446
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 3 Oct 2026