Cairn
NousResearch/hermes-agent

Cron script execution backend routing fixes

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

These items address how cron/scheduled script jobs are routed to the correct execution backend or terminal target, including a bug where the backend setting was ignored and a fix to validate missing scripts at creation time.

Open issues1

  • Issue#29849[Bug]: `no_agent=True` cronjob script execution ignores `terminal.backend`, always runs on scheduler host

Open PRs1

  • PR#80404fix(cron): run script jobs through declared execution targets

1 PR closed without merging

From the close comments: stale or abandoned 1

  • #29896 fix(cron): reject missing cron scripts at create-time with scheduler-host hint · stale or abandoned
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/29849.json
cluster/29849.md