NousResearch/hermes-agent

Cron missed fires and scheduler health reporting

Cluster 107168. Data as of 2026-10-26 12:29 UTC

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

open issues

open PRs

items grouped

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

Next step: read #112830, then check it covers your case.

Read #112830 Pick up a Lab task

A bug and related fixes addressing silent skipping of missed cron job fires in non-default profiles, and improving visibility of satellite scheduler health in cron status and doctor commands.

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.

#112830 fix(cron): report satellite scheduler health and missed fires

merged to main

files: hermes_cli/cron.py, tests/cron/test_cronjob_gateway_liveness.py, tests/hermes_cli/test_cron.py, tests/hermes_cli/test_cron_dispatch_visibility.py, tests/hermes_cli/test_cron_satellite_diagnostics.py, tests/hermes_cli/test_gateway_multiplex_served_record.py, website/docs/user-guide/features/cron.md, website/docs/user-guide/multi-profile-gateways.md

1 PR closed without merging

From the close comments: superseded by another PR 1

#107181 fix(cron): surface missed fires and clarify satellite gateway status (#107168) · superseded by another PR → #112830

Closed issues · 1

Closed#107168[Bug]: Cron jobs in non-default profiles are ticked only by the Desktop scheduler — missed fires are silently skipped (no catch-up, no incident), and `cron status`/`doctor` report nothing wrong

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

Merged PRs: #112830
Closed issues: 1
Attempts: 1 PR closed without merging
Fix link checked: 18 Sep 2026

For your agent

The same facts, typed.

cluster/107168.json
cluster/107168.md