# NousResearch/hermes-agent · Cron overlap losers excluded from failure tracking

## Open now

- 1 issue, 1 PR open on GitHub.
- #100946: Cron fire-claim overlap losers should not be recorded as failed executions
- PR #100976: fix(cron): stop overlap losers from inflating failure history

These items address a specific cron scheduling issue where executions that lose a fire-claim overlap race were being incorrectly recorded as \`failed\`. The work focuses on preventing those overlap losers from affecting failure history or counts.

## TL;DR

- 3 member(s): 1 open issue(s), 0 closed issue(s), 1 open PR(s), 0 merged PR(s), 1 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.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.

## Open related issues

- #100946: Cron fire-claim overlap losers should not be recorded as failed executions

## Prior & competing PRs

- **#100976: fix(cron): stop overlap losers from inflating failure history**. open
  - maintainer direction: category `uncategorized`; implication `needs_llm`; refs `#100976`
  - files: `cron/executions.py`, `cron/scheduler.py`, `tests/cron/test_execution_ledger.py`
- **#116591: fix(cron): neutralize fire-claim overlap losers**. closed without merge
  - maintainer direction: category `silent_close`; implication `active`

## Fix status

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