# NousResearch/hermes-agent · Cron worker kill/failure not recorded on job

## Open now

- Nothing open on GitHub.

These items address cases where cron workers killed or failing after job adoption leave the job record without updated status, incident, or failure delivery. The work involves detecting and recording such outcomes on the job.

## TL;DR

- 4 member(s): 0 open issue(s), 1 closed issue(s), 0 open PR(s), 0 merged PR(s), 3 PR(s) closed without merging.
- No fix has been merged to main; one or more PRs were attempted (see below).
- **Recommended:** review the prior/competing PR(s) below. A fix was attempted but not merged; your case may extend or revive that work.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `unresolved`. This is distinct from the fix status above. Weigh it yourself.

## How this cluster was grouped

- Link evidence (`STRUCTURAL_SPANNING`): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
- Pairwise link density `0.50`: the share of member 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.

## Closed / duplicate issues

- #120328: \[Bug\]: cron worker killed after adoption (e.g. OOM) leaves the job record untouched — no last_status, no incident, no failure delivery

## Prior & competing PRs

- **#120347: fix(cron): project recovered worker failures**. closed without merge
  - maintainer direction: category `implemented_elsewhere`; implication `superseded`
- **#120360: cron: record killed post-adopt worker on the job (incident, delivery, log)**. closed without merge
  - maintainer direction: category `uncategorized`; implication `needs_llm`
- **#120391: fix(cron): record a restart-safe worker's unknown outcome on the job**. closed without merge
  - maintainer direction: category `silent_close`; implication `active`

## Fix status

- No merged fix on record.
- Subsystem: `cron`