Cairn
NousResearch/hermes-agent

Cron jobs not executing or reporting status, with related fixes

Cluster 2788 · cron. Data as of

Nothing open on GitHub. Fix attempted, not merged.

The short answer

0open issues
0open PRs
7items grouped
Known?
Yes. 7 related items grouped here, 3 issues already closed.
Fix event
No fix has been merged to main. 4 PRs closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
Nothing open on GitHub.

Most members concern cron jobs not running, staying in a scheduled state, or giving little diagnostic information, along with proposed changes to how 'run' executes and to gateway-not-running warnings. One member, about propagating CLI command exit codes, is less clearly tied to cron.

Open issues0

No open issues.

Open PRs0

No open pull requests.

4 PRs closed without merging

From the close comments: done elsewhere 1 · stale or abandoned 1 · won't fix / by design 1 · other 1

  • #2793 fix(cron): warn user when creating cron job if gateway is not running · other → #51790
  • #17516 fix(cron): action='run' executes inline when no gateway ticker is running · stale or abandoned → #16612
  • #23074 fix(cron): action='run' now executes job immediately instead of just scheduling (#21867) · done elsewhere → 65d7c7f
  • #43645 fix: propagate CLI command exit codes · won't fix / by design
Closed issues · 3
  • Closed#2788[Bug]: Cron jobs never run or when it failed, no useful information is recorded
  • Closed#16612Bug: cronjob run 无法实际触发执行 (job stuck in state: scheduled)
  • Closed#21867[Bug]: Cron doesn't work!
How this cluster was grouped
  • Link evidence (partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
  • Members outside that structural core may belong to a different underlying problem.
  • Pairwise link density 0.22: 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
3
Attempts
4 PRs closed without merging

For your agent

The same facts, typed.

cluster/2788.json
cluster/2788.md