Cairn
NousResearch/hermes-agent

Cron store write failures block all scheduled jobs

Cluster 132932 · cron. Data as of

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

A bug where an unwritable or full cron store causes the scheduler to abort all jobs on the profile; fixes ensure dispatching continues despite persistence errors, with outage visibility in status, metrics, and diagnostics.

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.

  • #133283 fix(cron): a full or read-only cron store no longer stops the scheduler; jobs catch up once on recovery and the outage shows in cron status, doctor, metrics and the home channel (#132932, salvage #132933)

    merged to main

    files: agent/monitoring/cron_health.py, agent/monitoring/gateway_health_export.py, contributors/emails/[email protected], cron/constants.py, cron/executions.py, cron/jobs.py, cron/occurrences.py, cron/scheduler.py, cron/scheduler_ownership.py, cron/scheduler_tick.py, cron/store_health.py, cron/unreachable_retry.py, gateway/cron_store_notices.py, gateway/run_startup.py, hermes_cli/cron.py, hermes_cli/doctor.py, hermes_cli/doctor_state.py, locales/af.yaml, locales/ar.yaml, locales/de.yaml (+19 more)

1 PR closed without merging

From the close comments: done elsewhere 1

  • #132933 fix(cron): keep dispatching when the due scan cannot persist its repairs · done elsewhere → 152aa69, #133283
Closed issues · 1
  • Closed#132932[Bug]: a cron store that cannot be written stops every job on the profile (due scan aborts)
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
#133283
Closed issues
1
Attempts
1 PR closed without merging
Fix link checked
7 Oct 2026

For your agent

The same facts, typed.

cluster/132932.json
cluster/132932.md