# NousResearch/hermes-agent · Add provider/model/token context to cron failure notifications

## Open now

- 3 issues, 2 PRs open on GitHub.
- #43168: feat(cron): include provider/model/token context in failed job notifications
- #43170: feat(cron): include provider/model/token context in failed job error notifications
- #43177: feat(cron): attach failure diagnostic context to cron error notifications
- PR #43176: feat(cron): enrich failure notifications with provider/model/token context
- PR #44079: \[verified\] add API diagnostics to cron failure notifications

These items all concern enriching cron job failure notifications with additional diagnostic context, specifically provider, model, and token information. The members are closely related and appear to represent iterations or duplicates of the same feature proposal.

## TL;DR

- 5 member(s): 3 open issue(s), 0 closed issue(s), 2 open PR(s), 0 merged PR(s), 0 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_PARTIAL`): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
- Members outside that structural core may belong to a different underlying problem.
- Pairwise link density `0.41`: 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

- #43168: feat(cron): include provider/model/token context in failed job notifications
- #43170: feat(cron): include provider/model/token context in failed job error notifications
- #43177: feat(cron): attach failure diagnostic context to cron error notifications

## Prior & competing PRs

- **#43176: feat(cron): enrich failure notifications with provider/model/token context**. open
  - maintainer direction: category `uncategorized`; implication `needs_llm`; refs `a5e06078b2ecb6201ed5332c88ab9df553d04c97`
  - files: `cron/scheduler.py`, `tests/cron/test_cron_failure_diagnostics.py`
- **#44079: \[verified\] add API diagnostics to cron failure notifications**. open
  - maintainer direction: category `duplicate_of`; implication `duplicate`; refs `#43176`, `#43168`, `#43170`, `#43177`, `#18551`, `#43176`
  - files: `agent/conversation_loop.py`, `cron/scheduler.py`, `tests/cron/test_scheduler.py`

## Fix status

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