Cron external worker config hook registration fix
Cluster 131764. Data as of
Nothing open on GitHub. Fix merged in #132438 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 #132438. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #132438. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items concern a bug where config.yaml shell hooks and outbound webhooks were not being registered for cron jobs running under an external worker, causing them to silently do nothing. The cluster covers the bug report, a fix attempt, and a follow-up salvage effort.
Open issues0
Open PRs0
Fixes on record
-
#132438 Config hooks and outbound webhooks fire for external-worker cron jobs (salvage #131831)
files:
cron/scheduler.py,tests/cron/test_external_worker_config_hooks.py
1 PR closed without merging
From the close comments: other 1
-
#131831 fix(cron): register the owning profile's config hooks in the external worker · other →
946eafd,8840751,#132438
Closed issues · 1
- Closed#131764Cron external worker never registers config.yaml shell hooks — hooks silently dead for every scheduled job under a systemd gateway
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
- #132438
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 3 Oct 2026