Cairn

Cron recurring-to-one-shot transition bug fixes

NousResearch/hermes-agent · cluster 124222 · 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 recurring cron job converted to a one-shot behaves incorrectly — either being deleted without firing or mishandling the run budget. The group covers a bug report and related fix attempts around this specific transition scenario.

Open issues1

  • Issue#124222[Bug]: a recurring cron job that has already run is deleted without firing when changed to a one-shot

Open PRs2

  • PR#124224fix(cron): a recurring job turned one-shot starts a fresh run budget
  • PR#124410fix(cron): a recurring job edited into a one-shot fires instead of being deleted
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.

cluster/124222.json
cluster/124222.md