Cron ticker thread resilience during startup failures
Cluster 111010. Data as of
Nothing open on GitHub. Fix merged in #111079 on 14 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 #111079. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #111079. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These issues and pull requests address a bug where the cron scheduler daemon thread silently dies during gateway startup, causing no jobs to fire. The work focuses on keeping or respawning the ticker thread through startup recovery and marker-write failures.
Open issues0
Open PRs0
Fixes on record
-
#111079 Multiplex gateway: cron ticker survives startup and is respawned, Discord-thread Kanban subs deliver under profile_routes, secondary-profile skills dispatch (#111010, #110919, #110695; salvage #111034, #110928, #110698)
files:
cron/scheduler_provider.py,cron/scheduler_thread.py,gateway/kanban_watchers_notifier.py,gateway/run.py,hermes_cli/kanban.py,hermes_cli/kanban_db_notify.py,hermes_cli/kanban_parser.py,tests/cron/test_ticker_startup_survival.py,tests/gateway/test_kanban_routed_transport.py,tests/hermes_cli/test_kanban_notify.py,tests/tui_gateway/test_protocol.py,tui_gateway/methods_tools.py,website/docs/user-guide/features/kanban.md
2 PRs closed without merging
From the close comments: merged via another change 1 · superseded by another PR 1
-
#111034 fix(cron): keep the ticker thread alive through startup recovery and marker writes · merged via another change →
23ef640,a8b7af8,#111079 -
#111182 Cron ticker thread survives startup recovery and marker-write failures (#111010, salvage #111034) · superseded by another PR →
8fce4ba,45b4220,#111034
Closed issues · 1
- Closed#111010[Bug]: Cron scheduler daemon thread silently dies on gateway startup — no jobs fire
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
- #111079
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 14 Sep 2026