cron adopted external worker re-exec and payload bugs

NousResearch/hermes-agent · cluster 124827 · cron

Data as of

Nothing open on GitHub. Fix merged in #134358. Check it covers your case.

The short answer

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

Multiple fixes addressing a scenario where an adopted external worker incorrectly re-executes, potentially losing or prematurely deleting its one-shot handoff payload. Changes include suppressing bootstrap relaunch, correcting import order, and preventing re-exec after payload deletion.

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.

  • #134358 Cron external workers no longer relaunch after their ack and leave the run unknown (#124827, salvage #133720)

    merged to main

    files: contributors/emails/[redacted:email], cron/AGENTS.md, cron/scheduler.py, cron/worker_bootstrap.py, tests/cron/test_restart_safe_worker.py

4 PRs closed without merging

From the close comments: done elsewhere 3 · superseded by another PR 1

  • #124847 fix(cron): suppress bootstrap relaunch inside an adopted external worker · done elsewhere → de116d8, #134358, #133720, #124827
  • #124855 fix(cron): stop an adopted external worker from re-exec'ing and losing its payload (#124827) · done elsewhere → de116d8, #134358, #133720, #124827
  • #124886 fix(cron): import run_agent before consuming worker handoff payload · done elsewhere → de116d8, #134358, #133720, #124827
  • #133720 fix(cron): a source-update relaunch replays the external worker before its ack · superseded by another PR → 4d3b390, 873dd42, #134358
Closed issues · 1
  • Closed#124827fix(cron): adopted external worker can re-exec after deleting one-shot payload, leaving run unknown
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.33: 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
#134358
Closed issues
1
Attempts
4 PRs closed without merging
Fix link checked
7 Oct 2026

For your agent

The same facts, typed.