# NousResearch/hermes-agent · Discord reply-target missing causes send failures

## Open now

- Nothing open on GitHub.

These issues and PRs address a bug where a deleted or invalid reply target causes Discord message sending to crash or lose content. The fixes involve dropping invalid reply references and setting appropriate flags to handle missing reply targets gracefully.

## TL;DR

- 4 member(s): 0 open issue(s), 1 closed issue(s), 0 open PR(s), 1 merged PR(s), 2 PR(s) closed without merging.
- A fix was merged to main in PR #11557. Verify it addresses your case.
- **Recommended:** read PR #11557 (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-11557`. 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

- #11342: Discord: deleted reply target crashes the whole chunked send (missing \`fail_if_not_exists=False\`)

## Prior & competing PRs

- **#11557: fix(discord): drop invalid reply references + propagation regression guard**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `gateway/platforms/discord.py`, `tests/gateway/test_discord_reply_mode.py`, `tests/gateway/test_discord_send.py`
- **#11344: fix(discord): don't lose the whole reply when reply-target vanishes**. closed without merge
  - maintainer direction: category `implemented_elsewhere`; implication `superseded`; refs `a448e7a04d22babb9a9c6c9bfc67ee6306cde2c7`, `#11557`
- **#11348: fix(discord): drop invalid reply references**. closed without merge
  - maintainer direction: category `merged_via`; implication `superseded`; refs `#11557`

## Fix status

- Merged to main in PR #11557 (cited above). No release data is tracked. Verify downstream.
- Fix last verified (merged) `2026-04-17`. This confirmation is old and may be out of date (a revert/reopen would not have invalidated it here); re-verify.