Cairn
NousResearch/hermes-agent

Cron one-shot job incorrectly shows failure status

Cluster 71760 · 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.

A bug causes cron jobs that run once and are removed after clean completion to be incorrectly reported as having a failure status. Related pull requests address this false status reporting.

Open issues1

  • Issue#71760hermes cron run reports 'Ran now: failed.' for a run whose agent session completed cleanly

Open PRs2

  • PR#71768fix(cron): report success for one-shot jobs removed after completion (#71760)
  • PR#71981fix(cron): report success for one-shot jobs removed after completion (#71760)
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/71760.json
cluster/71760.md