Cron liveness detection and multiplex profile fixes
Cluster 121881 · hermes cli. Data as of
Nothing open on GitHub. Fix merged in #126156 on 28 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 #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
- Nothing open on GitHub.
These items address false 'no gateway running' warnings when an in-process serve ticker is active, and correct cron behavior under multiplex topologies including liveness checks, manual-run delivery, managed routes, and worker secrets scoped to the owning profile.
Open issues0
Open PRs0
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: done elsewhere 1
-
#121921 fix(cron): treat a fresh serve ticker as scheduler-alive (#121881) · done elsewhere →
fc15ec8,dd00040,1744a19,#121881,#99631,#99579,#121921,#99613
Closed issues · 1
- Closed#121881[Bug]: hermes cron status/list report 'No gateway is running on this host — cron jobs will NOT fire' in the desktop topology while the in-process serve ticker is alive and jobs fire normally
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
- Subsystem
- hermes cli
- Merged PRs
- #126156
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 28 Sep 2026