Cairn

Cron reliability fixes for SSH-isolated backends

NousResearch/hermes-agent · cluster 107485

Data as of

Nothing open on GitHub. Fix merged in #108945. Check it covers your case.

The short answer

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

These items address cron scheduling problems in SSH-isolated backends, specifically around idle-exit killing running executions, missed slots during restart gaps, and a new opt-out for post-downtime catch-up firing.

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.

  • #108945 fix(cron): fire one catch-up for a slot missed during a restart gap (#107485)

    merged to main

    files: cli-config.yaml.example, cron/AGENTS.md, cron/jobs.py, cron/occurrences.py, hermes_cli/config_defaults.py, tests/cron/test_catchup_policy.py, tests/cron/test_cron_timezone_migration_catchup.py, tests/cron/test_jobs.py, tests/cron/test_missed_window_catchup.py, website/docs/developer-guide/cron-internals.md, website/docs/user-guide/features/cron.md

3 PRs closed without merging

From the close comments: duplicate 2 · superseded by another PR 1

  • #106255 cron: add skip_missed_runs to opt out of post-downtime catch-up firing · superseded by another PR → 36b1a6e, #108945, #107485, #104981
  • #107503 fix(dashboard): keep SSH-isolated backends alive during in-process cron · duplicate → a6c5b7a, #108945, #107485
  • #107552 fix(cron): count in-flight cron executions in the SSH-isolated backend idle-exit probe · duplicate → #107503, #107485
Closed issues · 1
  • Closed#107485Cron scheduler hosted in SSH-isolated backend: idle-exit kills running cron executions and silently skips scheduled slots
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.40: 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
#108945
Closed issues
1
Attempts
3 PRs closed without merging
Fix link checked
12 Sep 2026

For your agent

The same facts, typed.

cluster/107485.json
cluster/107485.md