Cairn
NousResearch/hermes-agent

Cron reporting accuracy and scheduler lifecycle improvements

Cluster 83340 · cron. Data as of

Nothing open on GitHub. Fix merged in #86682 on 15 Aug 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 #86682. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this resolved, deciding PR #86682. That is separate from the fix event.
Still open
Nothing open on GitHub.

These members address incorrect status reports for cron runs and consolidate several scheduler lifecycle issues including guard leaks, alerts, DNS fallback, and cleanup bounds. The work spans CLI background dispatch verdict accuracy and broader scheduler robustness.

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.

  • #86682 fix(cron): consolidate scheduler-lifecycle salvage — guard-leak tick continuation, failure alerts, DNS fallback, bounded cleanup, CLI background verdict

    merged to main

    files: contributors/emails/[redacted:email], cron/scheduler.py, hermes_cli/cron.py, tests/cron/test_cleanup_timeout.py, tests/cron/test_parallel_pool.py, tests/cron/test_recurring_wedge_selfheal.py, tests/cron/test_run_one_job.py, tests/cron/test_scheduler.py, tests/hermes_cli/test_cron.py, website/docs/user-guide/features/cron.md

1 PR closed without merging

From the close comments: merged via another change 1

  • #83365 fix(cli): report background-dispatch cron runs without false 'failed' · merged via another change → #86682
Closed issues · 1
  • Closed#83340hermes cron run reports 'failed' without executing the job (desktop-app shell)
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
#86682
Closed issues
1
Attempts
1 PR closed without merging
Fix link checked
15 Aug 2026

For your agent

The same facts, typed.

cluster/83340.json
cluster/83340.md