Cairn
NousResearch/hermes-agent

Cron multiplex ticker per-profile isolation fixes

Cluster 74878 · cron. Data as of

Nothing open on GitHub. Fix merged in #101245 on 2 Sep 2026. Check it covers your case.

The short answer

0open issues
0open PRs
3items grouped
Known?
Yes. 3 related items grouped here, 1 issue already closed.
Fix event
A fix was merged to main in PR #101245. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this resolved, deciding PR #101245. That is separate from the fix event.
Still open
Nothing open on GitHub.

These items concern bugs and fixes around cron job multiplexing where secondary profiles' tickers were missing or errors were not properly isolated per profile. The work addresses tick delivery, port binding, and fail-closed satellite behavior in the multiplex cron system.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

  • #101245 fix(cron): multiplex ticks isolate per profile, fire the bound port, deliver satellites fail-closed (#74878 #100489 #101113 #86519, salvage #70747 #84755 #96944)

    merged to main

    files: cron/notepad.py, cron/scheduler.py, cron/scheduler_provider.py, cron/suggestions.py, hermes_cli/web_server.py, tests/cron/test_cron_multiplex_desktop_ticker_scope.py, tests/cron/test_cron_multiplex_shared_route_delivery.py, tests/cron/test_notepad.py, tests/cron/test_scheduler_provider.py, tests/cron/test_suggestions.py, tests/hermes_cli/test_cron_fire_dashboard.py, website/docs/user-guide/multi-profile-gateways.md

1 PR closed without merging

From the close comments: merged via another change 1

  • #74952 fix(cron): isolate per-profile errors in multiplex ticker (#74878) · merged via another change → eed481b, #101245
Closed issues · 1
  • Closed#74878multiplex_profiles: secondary profiles' cron jobs never fire — no ticker, and no warning
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.00 means 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

At a glance

Subsystem
cron
Merged PRs
#101245
Closed issues
1
Attempts
1 PR closed without merging
Fix link checked
2 Sep 2026

For your agent

The same facts, typed.

cluster/74878.json
cluster/74878.md