Cairn
NousResearch/hermes-agent

Cron delivery fixes for relay-fronted targets

Cluster 86249 · cron. Data as of

Nothing open on GitHub. Fix merged in #96832 on 28 Aug 2026. Check it covers your case.

The short answer

0open issues
0open PRs
4items grouped
Known?
Yes. 4 related items grouped here, 1 issue already closed.
Fix event
A fix was merged to main in PR #96832. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
Nothing open on GitHub.

These issues and pull requests address cron job delivery failures when targets are fronted by a relay, covering missing transport registration, gateway forwarding, and manual-run prompt handling. No resolution status is assumed.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

  • #96010 fix(cron): manual run on relay-fronted targets — gateway forward + accurate error

    merged to main

    files: cron/scheduler.py, tests/cron/test_cron_relay_run_forward.py, tests/cron/test_relay_fronted_delivery.py, tools/cronjob_tools.py

  • #96832 fix(cron): manual-run prompt no longer dropped on the relay-fronted gateway forward

    merged to main

    files: cron/jobs.py, cron/scheduler.py, gateway/platforms/api_server.py, tests/cron/test_cron_relay_run_forward.py, tests/gateway/test_api_server_jobs.py, tools/cronjob_tools.py, website/docs/guides/cron-troubleshooting.md

1 PR closed without merging

From the close comments: done elsewhere 1

  • #86489 fix(cron): out-of-process relay-fronted delivery via gateway loopback · done elsewhere → 5cc47c9, #86249, #96010, #96832
Closed issues · 1
  • Closed#86249Relay-fronted cron delivery: out-of-process runs have no transport (relay registers no standalone_sender_fn) — scheduled reports never reach Discord on Hermes Cloud
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.50: 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
Merged PRs
#96010, #96832
Closed issues
1
Attempts
1 PR closed without merging
Fix link checked
28 Aug 2026

For your agent

The same facts, typed.

cluster/86249.json
cluster/86249.md