# NousResearch/hermes-agent · Cron dispatch-failure notice credential/profile binding

## Open now

- Nothing open on GitHub.

These items address a bug where cron crash or dispatch-failure notices use incorrect credentials or profile scope, particularly on multi-profile gateway setups. The work involves binding the correct profile's secret scope when sending these notices.

## 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 #132446. Verify it addresses your case.
- **Recommended:** read PR #132446 (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-132446`. 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

- #131585: \[Bug\]: Cron dispatch-failure notice still isn't delivered on multi-profile gateways (#123401 follow-up)

## Prior & competing PRs

- **#132446: Cron crash notices use the firing profile's credentials (salvage #130431)**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `contributors/emails/skyeyesec333@users.noreply.github.com`, `cron/scheduler.py`, `tests/cron/test_restart_safe_worker.py`
- **#130431: fix(cron): bind the profile secret scope for the dispatch-failure notice**. closed without merge
  - maintainer direction: category `implemented_elsewhere`; implication `superseded`; refs `8d15ca4878`, `c8815a52c5`, `#132446`

## Fix status

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