Desktop cron suppressed by gateway present at startup
Cluster 126822. Data as of
Nothing open on GitHub. Fix merged in #126973 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 #126973. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #126973. That is separate from the fix event. - Still open
- Nothing open on GitHub.
A regression causes the Desktop backend to never start its cron ticker when a gateway is live at startup, so cron permanently stops for all profiles if that gateway later disappears. The members address detection, stand-down re-probing, and takeover behavior around this lifecycle gap.
Open issues0
Open PRs0
Fixes on record
-
#126973 fix(desktop): Desktop cron takes over when a gateway live at backend start goes away
files:
hermes_cli/web_server.py,tests/hermes_cli/test_desktop_cron_ticker_gateway_standdown.py,tests/hermes_cli/test_desktop_cron_ticker_profiles.py
2 PRs closed without merging
From the close comments: done elsewhere 1 · superseded by another PR 1
Closed issues · 1
- Closed#126822Desktop backend never starts its cron ticker if a gateway was live at backend startup, so cron stops for every profile when that gateway dies later (regression)
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
- Merged PRs
- #126973
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 28 Sep 2026