You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are running our own slack bridge, but messages sent from Slack, that contain a URL, which generates a preview are not sent to the Matrix room. We enabled Debug Logs on the Bridge and on Synapse itself, but could not find any error messages. Instead it seems, that the message is somehow filtered by the bridge.
I tried to reproduce it and cannot; messages with link previews come through, in both RTM and webhook mode.
The message would get quietly dropped by the bridge if it was sent by the same Slack bot that's doing the bridge – can you confirm that this is not the case? It is broken for all users in that channel? And, just in case, do other messages in that channel come through?
Thank you for looking into this @tadzik! I was debugging this together with @samuel-p and I was the one who did the test above.
The message would get quietly dropped by the bridge if it was sent by the same Slack bot that's doing the bridge – can you confirm that this is not the case?
I was sending the message with my own Slack user, the one that shows in logs as SLACK_USER_ID_REDACTED, not a bot user.
It is broken for all users in that channel?
Yes, we experience this both in a large public channel, and in a test channel that we set up to troubleshoot this.
And, just in case, do other messages in that channel come through?
Yes, other messages that do not have a preview in Slack also come through.
Are there any other logs that we could provide beyond the ones above?
We are running our own slack bridge, but messages sent from Slack, that contain a URL, which generates a preview are not sent to the Matrix room. We enabled Debug Logs on the Bridge and on Synapse itself, but could not find any error messages. Instead it seems, that the message is somehow filtered by the bridge.
The text was updated successfully, but these errors were encountered: