Cairn

Cron skipped/refused executions now recorded properly

NousResearch/hermes-agent · cluster 127723 · 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 issues and fixes address cases where cron job occurrences were silently dropped or skipped without writing an execution row, such as when a job is refused or already running. The changes ensure skipped and refused occurrences are recorded rather than silently omitted.

Open issues1

  • Issue#127723[Bug]: Stuck cron execution can skip later recurring occurrences without an execution row

Open PRs2

  • PR#127741fix(cron): write a skipped execution row when a tick skips an already-running job
  • PR#127756fix(cron): record refused occurrences instead of dropping them silently (#127723)
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/127723.json
cluster/127723.md