Cron ignoring managed-scope gateway profile routes
Cluster 121212 · cron. Data as of
1 open item. Fix merged in #126156 on 28 Sep 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 #126156. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #126156. That is separate from the fix event. - Still open
- 0 issues and 1 PR.
These issues and PRs concern cron jobs failing to read managed-scope gateway.profile_routes, causing incorrect preflight blocks and delivery failures. Related work extends profile-aware behavior to liveness, manual runs, and worker secrets under multiplex.
Open issues0
Open PRs1
- PR#121595fix(cron): read managed-scope gateway.profile_routes in preflight (#121212)
Fixes on record
-
#126156 cron under multiplex: liveness, manual-run delivery, managed routes, degraded-send retention and worker secrets follow the job's owning profile (#121881 #99579 #99631 #124248 #120330 #125363 #121212 #121929)
files:
contributors/emails/[redacted:email],cron/jobs.py,cron/scheduler.py,cron/scheduler_delivery.py,cron/scheduler_preflight.py,hermes_cli/cron.py,tests/cron/test_cron_reconnect_only_rejection.py,tests/cron/test_external_worker_secret_sources.py,tests/cron/test_preflight_managed_routes.py,tests/hermes_cli/test_cron.py,tests/hermes_cli/test_cron_satellite_diagnostics.py,tests/tools/test_cronjob_run_immediate.py,tests/tools/test_cronjob_run_primary_routed.py,tools/cronjob_tools.py
1 PR closed without merging
From the close comments: superseded by another PR 1
-
#121215 fix(cron): honor managed profile routes during preflight · superseded by another PR →
#126156
Closed issues · 1
- Closed#121212Cron: satellite profiles ignore `gateway.profile_routes` pinned in the managed scope (`/etc/hermes/config.yaml`), so preflight false-blocks and routed delivery fails closed
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
- Subsystem
- cron
- Merged PRs
- #126156
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 28 Sep 2026