Cairn
NousResearch/hermes-agent

Cron catch-up incorrectly re-fires completed recurring jobs

Cluster 104312 · cron. Data as of

1 open item. Fix merged in #104977 on 7 Sep 2026. Check it covers your case.

The short answer

1open issue
0open PRs
3items grouped
Known?
Yes. 3 related items grouped here, 0 issues already closed.
Fix event
A fix was merged to main in PR #104977. 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
1 issue and 0 PRs.

These members concern a bug where cron catch-up logic re-fires recurring jobs whose scheduled runs already completed, triggered by gateway restarts or snapshot rollbacks. Two associated fixes address consulting execution history before re-firing.

Open issues1

  • Issue#104312Cron catch-up re-fires a recurring job whose scheduled occurrence already ran and completed after gateway restart

Open PRs0

No open pull requests.

Fixes on record

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

  • #104977 fix(cron): completed scheduled runs no longer replay after snapshot rollback (#104790)

    merged to main

    files: contributors/emails/[redacted:email], cron/executions.py, cron/jobs.py, cron/occurrences.py, cron/scheduler.py, cron/scheduler_provider.py, tests/cron/test_parallel_pool.py, tests/cron/test_restart_safe_worker.py, tests/cron/test_scheduled_occurrence.py, tests/cron/test_scheduler_provider.py, tests/plugins/test_chronos_cron.py, tests/tools/test_delegate_control_actions.py, website/docs/user-guide/features/cron.md

1 PR closed without merging

From the close comments: superseded by another PR 1

  • #104323 fix(cron): consult the execution ledger before catch-up re-firing a recurring job (#104312) · superseded by another PR → #104977
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
#104977
Closed issues
0
Attempts
1 PR closed without merging
Fix link checked
7 Sep 2026

For your agent

The same facts, typed.

cluster/104312.json
cluster/104312.md