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 just migrated from the previous adapter to this one, and we also moved from the Slack-developed bot to using a custom Slack app per the instructions in this docs.
In the migration, we noticed the bot stopped to respond to messages sent via Slack workflow. We have workflows that we use for deploy, that eventually trigger a message like the following:
If the message is posted by a user, the bot responds and handles the action. If the message is posted by the workflow, the bot doesn't handle the message.
I enabled the debug mode, and I see the message is being discovered by the bot. However it doesn't handle it. It is worth noting the payload of a message sent by the workflow is a subtype bot_message, which is slightly different variant of a message.
What type of issue is this? (place an x in one of the [ ])
bug
enhancement (feature request)
question
documentation related
testing related
discussion
Requirements (place an x in each of the [ ])
I've read and understood the Contributing guidelines and have done my best effort to follow them.
In case of the same message sent from the workflow, the bot simply doesn't reach. It is almost as if the message is not parsed/discovered, despite the text is the same.
Attachments:
This is the log when the message is sent from the workflow:
Worth mentioning that when the message is sent by the workflow, the adapter doesn't even output a message line. It is almost as if it is unable to read the message at all, no matter if it is a mention or not.
The following is the output for a message that is not a mention. The last 4 lines output the parsed message. These lines are never present for a message sent by the workflow.
Description
We just migrated from the previous adapter to this one, and we also moved from the Slack-developed bot to using a custom Slack app per the instructions in this docs.
In the migration, we noticed the bot stopped to respond to messages sent via Slack workflow. We have workflows that we use for deploy, that eventually trigger a message like the following:
If the message is posted by a user, the bot responds and handles the action. If the message is posted by the workflow, the bot doesn't handle the message.
I enabled the debug mode, and I see the message is being discovered by the bot. However it doesn't handle it. It is worth noting the payload of a message sent by the workflow is a subtype bot_message, which is slightly different variant of a message.
What type of issue is this? (place an
x
in one of the[ ]
)Requirements (place an
x
in each of the[ ]
)Bug Report
Filling out the following details about bugs will help us solve your issue sooner.
Reproducible in:
hubot-slack version: 3.0.2
node version: 20.x
OS version(s): Linux
Steps to reproduce:
Expected result:
The bot should properly detect mentions originating from a workflow, and handle the message.
Actual result:
The bot receves the message, but it ignores the message. The following are the logs from a handled message:
In case of the same message sent from the workflow, the bot simply doesn't reach. It is almost as if the message is not parsed/discovered, despite the text is the same.
Attachments:
This is the log when the message is sent from the workflow:
This is the log when the message is sent by a user:
Worth mentioning that when the message is sent by the workflow, the adapter doesn't even output a message line. It is almost as if it is unable to read the message at all, no matter if it is a mention or not.
The following is the output for a message that is not a mention. The last 4 lines output the parsed message. These lines are never present for a message sent by the workflow.
The text was updated successfully, but these errors were encountered: