Cairn

Cron self-scheduling and chained job booking fixes

NousResearch/hermes-agent · cluster 130896 · 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 issues where cron jobs fail to book their own next run, particularly when agent scheduling is enabled or chaining is involved. The work includes clarifications and fixes to self-scheduling behavior in the cron system.

Open issues1

  • Issue#130896Cron: with allow_agent_scheduling on, the run note can stop a job from booking its own next run

Open PRs2

  • PR#130899fix(cron): clarify self-scheduling tasks
  • PR#130911fix(cron): let a chained job book its own next 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
0
Attempts
0 PRs closed without merging

For your agent

The same facts, typed.

cluster/130896.json
cluster/130896.md