Cairn
NousResearch/hermes-agent

Cron repeat jobs incorrectly marked completed early

Cluster 29392 · cron. Data as of

1 open item. Fix attempted, not merged.

The short answer

0open issues
1open PR
3items grouped
Known?
Yes. 3 related items grouped here, 1 issue 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
0 issues and 1 PR.

A bug where repeating cron jobs are prematurely marked as completed after their first run, along with related fixes to reschedule such jobs correctly based on remaining repeats.

Open issues0

No open issues.

Open PRs1

  • PR#29811fix(cron): reschedule one-shot jobs with remaining repeats instead of marking completed

1 PR closed without merging

From the close comments: partial fix 1

  • #29455 fix(cron): promote "2m" + repeat>1 to recurring interval (#29392) · partial fix → #29392
Closed issues · 1
  • Closed#29392[BUG] Scheduler prematurely marks repeating cron jobs as 'completed' after first successful run
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
1
Attempts
1 PR closed without merging

For your agent

The same facts, typed.

cluster/29392.json
cluster/29392.md