# NousResearch/hermes-agent · Cron recovery misidentifies live owner on start-time drift

## Open now

- Nothing open on GitHub.

These items address a bug where cron's recovery logic incorrectly rejects a live process as the owner when its start-time fingerprint differs by a small amount (e.g., one second), causing running executions to be marked unknown. The fix treats a drifted-but-close start-time as still belonging to a live owner.

## TL;DR

- 3 member(s): 0 open issue(s), 1 closed issue(s), 0 open PR(s), 1 merged PR(s), 1 PR(s) closed without merging.
- A fix was merged to main in PR #117584. Verify it addresses your case.
- **Recommended:** read PR #117584 (and any competing PRs below) before filing. Confirm the merged change covers your symptom.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `resolved` · deciding PR(s): `pr-117584`. 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.67`: 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

- #117505: cron: _owner_is_live() rejects a live process on an exact start-time compare, marking running executions unknown

## Prior & competing PRs

- **#117584: fix(cron): recovery keeps a live owner whose start-time fingerprint drifted by a second (#117505, salvage #117514)**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `cron/executions.py`, `gateway/delivery_ledger.py`, `gateway/platforms/api_server_runs.py`, `gateway/status.py`, `tests/cron/test_owner_start_time_drift.py`, `tests/gateway/test_owner_liveness_drift.py`, `tools/async_delegation.py`
- **#117514: fix(cron): treat a drifted start-time fingerprint as a live owner in recovery**. closed without merge
  - maintainer direction: category `merged_via`; implication `superseded`; refs `36ede56a66`, `#117584`

## Fix status

- Merged to main in PR #117584 (cited above). No release data is tracked. Verify downstream.
- Fix last verified (merged) `2026-09-20`.