Skip to content

[Fix] Discord thread replies show broken message references - #2017

Merged
mrubens merged 1 commit into
developfrom
fix/discord-thread-reply-references-2f6qwsy2lug5v
Sep 6, 2026
Merged

[Fix] Discord thread replies show broken message references#2017
mrubens merged 1 commit into
developfrom
fix/discord-thread-reply-references-2f6qwsy2lug5v

Conversation

@roomote-roomote

Copy link
Copy Markdown
Contributor

​Opened on behalf of @mrubens. Follow up by mentioning @roomote-roomote, in the web UI, or in Slack.

What changed

  • Stop adding Discord message_reference payloads to messages posted inside thread channels.
  • Preserve inline reply references for messages posted outside threads.
  • Cover both behaviors with focused Discord provider tests.

Why this change was made

The Discord provider attached a reply reference whenever replyToMessageId was present and set its channel_id to the outbound destination. For thread posts, callers can pass parent-channel starter or anchor message IDs, so the resulting cross-channel reference points at a message that does not exist in the thread and Discord renders a broken “Message could not be loaded” artifact.

Impact

Discord thread conversations no longer show broken or redundant inline reply cards. Ordinary channel and direct-message replies continue to reference their target message as before.

@roomote-community

roomote-community Bot commented Sep 1, 2026

Copy link
Copy Markdown
Contributor

No code issues found. See task

Reviewed b99635f

@mrubens
mrubens marked this pull request as ready for review September 6, 2026 13:21
@mrubens
mrubens merged commit 2e6e2e3 into develop Sep 6, 2026
17 checks passed
@mrubens
mrubens deleted the fix/discord-thread-reply-references-2f6qwsy2lug5v branch September 6, 2026 13:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant