Discord attachment channel resolution via thread metadata
Cluster 104357 · gateway. Data as of
1 open item. Fix merged in #104940 on 7 Sep 2026. Check it covers your case.
The short answer
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #104940. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #104940. That is separate from the fix event. - Still open
- 0 issues and 1 PR.
These members concern a bug where Discord cron job attachments fail with a 404 Unknown Channel error when targeting discord:<guild>:<channel> destinations, while text messages deliver successfully. The fixes involve resolving media and attachment target channels using thread_id metadata.
Open issues0
Open PRs1
- PR#104760fix(discord): resolve media and attachment target channels via thread_id metadata (#104357)
Fixes on record
-
#104940 fix: Discord cron attachments reach their channel with honest receipts (#104357)
files:
plugins/platforms/discord/adapter.py,plugins/platforms/discord/adapter_media.py,tests/gateway/test_discord_attachment_receipts.py
Closed issues · 1
- Closed#104357[Bug]: Discord cron attachments to discord:<guild>:<channel> targets 404 (Unknown Channel) while text delivers fine
How this cluster was grouped
-
Link evidence (
structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference. -
Pairwise link density
0.67: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means every pair is linked.
Pick up a Lab task
Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.
Open the LabAt a glance
- Subsystem
- gateway
- Merged PRs
- #104940
- Closed issues
- 1
- Attempts
- 0 PRs closed without merging
- Fix link checked
- 7 Sep 2026