Cron gateway multiplexer detection and profile delivery fixes
Cluster 97120 · cron. Data as of
Nothing open on GitHub. Fix merged in #99441 on 31 Aug 2026. Check it covers your case.
The short answer
- Known?
- Yes. 5 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #99441. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #99441. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items address bugs in cron's ability to detect a live multiplexer as a valid gateway, parse modern launchctl output, and correctly deliver profile jobs via their own bot, along with a crash-loop issue when the cron warning recommends installing a gateway under multiplex mode.
Open issues0
Open PRs0
Fixes on record
-
#99375 fix(cron): profile jobs deliver via their own bot and cron status stops lying (#94862 #99028 #98790, salvage x6)
files:
contributors/emails/[redacted:email],contributors/emails/[redacted:email],contributors/emails/[redacted:email],cron/scheduler.py,cron/scheduler_provider.py,gateway/run.py,hermes_cli/cron.py,hermes_cli/gateway.py,tests/cron/test_87033_cronjob_gateway_liveness.py,tests/cron/test_cron_home_target_profile_scope.py,tests/cron/test_cron_multiplex_profile_route_preflight.py,tests/cron/test_run_one_job.py,tests/cron/test_scheduler_provider.py,tests/cron/test_sessiondb_init_hang.py,tests/hermes_cli/test_cron_status_profile_isolation.py -
#99441 fix(cron): satellite profiles served by a live multiplexer count as gateway-alive (#97120, salvage #97558)
files:
hermes_cli/cron.py,hermes_cli/gateway.py,tests/cron/test_87033_cronjob_gateway_liveness.py,tests/gateway/test_multiplex_lifecycle.py
2 PRs closed without merging
From the close comments: done elsewhere 1 · merged via another change 1
Closed issues · 1
- Closed#97120Cron warning recommends `hermes gateway install` under multiplex; the gateway then refuses to start and the service crash-loops
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.40: 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 Lab