Cairn
NousResearch/hermes-agent

Cron job fails silently when script is missing

Cluster 105760 · cron. Data as of

2 open items. Fix attempted, not merged.

The short answer

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

A bug where cron jobs with missing or misplaced scripts register successfully but fail on every execution. Related fixes aim to reject invalid script paths at creation or update time rather than at runtime.

Open issues1

  • Issue#105760no_agent cron job: misplaced/missing script registers fine, then every fire fails with "Script not found"

Open PRs1

  • PR#105779fix(cron): reject broken script jobs before they can be scheduled

1 PR closed without merging

From the close comments: done elsewhere 1

  • #127690 fix(cron): reject missing script at create/update + profile-aware error path · done elsewhere → bd6eeef, #105760
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
1 PR closed without merging

For your agent

The same facts, typed.

cluster/105760.json
cluster/105760.md