Fix resuming exhausted finite recurring cron jobs

NousResearch/hermes-agent · cluster 125872 · cron

Data as of

3 open items. Fix attempted, not merged.

The short answer

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

These items address a bug where a finite recurring cron job that has exhausted its repeat count cannot be revived: both 'resume' and scheduling flags refuse to restart it and deflect to each other. The fixes allow resume to properly restart such an exhausted series.

Open issues1

  • Issue#125872cron: an exhausted recurring job (finite repeat) cannot be revived - resume and --at/--run-now each refuse and point at the other

Open PRs2

  • PR#125939fix(cron): restart a spent recurring series through plain resume (#125872)
  • PR#126932fix(cron): let resume restart an exhausted recurring job's series
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
0 PRs closed without merging

For your agent

The same facts, typed.