# NousResearch/hermes-agent · Cron delivery channel routing and name resolution

## Open now

- Nothing open on GitHub.

These issues and PRs concern bugs where cron-triggered deliveries route to incorrect channels and where channel names are not converted to IDs before delivery, specifically affecting Discord and Slack integrations.

## 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

- #2943: \[Bug\]: Discord API error in gateway

## Prior & competing PRs

- **#2946:  fix(cron): resolve channel names to IDs before Discord delivery **. closed without merge
  - maintainer direction: category `silent_close`; implication `active`
- **#2947: fix(cron): resolve channel names to IDs before Discord delivery**. closed without merge
  - maintainer direction: category `implemented_elsewhere`; implication `superseded`; refs `#3860`
- **#2948: fix(cron): resolve Discord/Slack channel names to IDs before delivery**. closed without merge
  - maintainer direction: category `uncategorized`; implication `needs_llm`; refs `3fad1e7cc`, `#3860`

## Fix status

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