Cairn
NousResearch/hermes-agent

Cron stale job catch-up control after host sleep

Cluster 111212 · cron. Data as of

2 open items. Fix attempted, not merged.

The short answer

1open issue
1open PR
3items grouped
Known?
Yes. 3 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. 1 PR closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
1 issue and 1 PR.

These items concern cron jobs firing stale or delayed executions after a host sleeps, and the addition of a per-job opt-out policy to suppress such catch-up runs. The group covers the reported behavior, visibility concerns, and related fixes.

Open issues1

  • Issue#111212Cron catch-up after host sleep fires stale jobs hours/days late with no visible policy or audit trail

Open PRs1

  • PR#111225fix(cron): stop stale jobs from running without per-job policy

1 PR closed without merging

From the close comments: other 1

  • #125360 fix(cron): per-job catch_up opt-out skips stale fires after host sleep · other → ba66199
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
Closed issues
0
Attempts
1 PR closed without merging

For your agent

The same facts, typed.

cluster/111212.json
cluster/111212.md