Cairn

Cron delivery status wrongly overwritten by post-delivery blips

NousResearch/hermes-agent · cluster 105861

Data as of

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

The short answer

0open issues
0open PRs
5items grouped
Known?
Yes. 5 related items grouped here, 1 issue already closed.
Fix event
A fix was merged to main in PR #109310. 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 fixes concern a specific bug where a successfully delivered cron run has its terminal status incorrectly overwritten—by 'ownership lost', 'interrupted by shutdown', or similar errors—when a fire-claim heartbeat or sample misses after delivery has already completed.

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.

  • #109310 fix(cron): long fenced deliveries no longer recorded as failed 'ownership lost' (#108341, #100401; salvage #106745)

    merged to main

    files: cron/jobs.py, tests/cron/test_claim_job_for_fire.py

  • #114332 A delivered cron run keeps its real status when the fire-claim sample misses afterwards (#105861, salvage #113283)

    merged to main

    files: cron/scheduler.py, tests/cron/test_fire_claim_lost_after_delivery.py, tests/cron/test_script_claim_heartbeat.py, tests/cron/test_shutdown_interrupt.py

2 PRs closed without merging

From the close comments: done elsewhere 1 · merged via another change 1

  • #105882 fix(cron): keep a delivered run's success through a transient post-delivery claim blip (#105861) · done elsewhere → #109310, #105861
  • #113283 fix(cron): a delivered run keeps its ok status when the fire-claim sample misses after delivery · merged via another change → #114332
Closed issues · 1
  • Closed#105861Cron agent jobs: successful delivery overwritten with "Interrupted by shutdown before terminal completion." when fire-claim heartbeat lapses mid-run
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.40: 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

Merged PRs
#109310, #114332
Closed issues
1
Attempts
2 PRs closed without merging
Fix link checked
17 Sep 2026

For your agent

The same facts, typed.

cluster/105861.json
cluster/105861.md