Can not trigger listener sometimes.

[yihchu]

Can not trigger listener sometimes.

[seratch]

Hi @yihchu, thanks for asking the question.

DEBUG Received file_shared message from: undefined, file_id: F03PP89C0BE

This log line indicates the message has an attached file. Thus, this one cannot be part of your screenshot. Please check the channel history again. Also, even when a message has attached files, as long as your message text contains "badger", your listener can react to the message for sure.

[yihchu]

Hi @yihchu, thanks for asking the question.

DEBUG Received file_shared message from: undefined, file_id: F03PP89C0BE

This log line indicates the message has an attached file. Thus, this one cannot be part of your screenshot. Please check the channel history again. Also, even when a message has attached files, as long as your message text contains "badger", your listener can react to the message for sure.

Hi @seratch ,please check this.
#642 (comment)

I reproduced, and I take a new screenshot and logs.

[seratch]

Hi @yihchu, I've checked your comment in #642 and tried to see the same situation on my end. However, my Hubot app does not miss any messages. Also, we do not see any outage / incident reports on the RTM API (= underlying WebSocket connectivity) at this moment.

The only possible cause that I can think of is that your Hubot app's WebSocket connection might be a bit unstable due to something specific to your network environment (or anything between Slack server and your Hubot app process). In this case, the Slack server-side could occasionally fail to send message events to your app.

To narrow the issue down, I would suggest trying to run the same app in a completely different setting (say, on a different cloud service) and see how it goes. If your situation persists regardless of where to run your Hubot app, something wrong may be happening to your workspace or Hubot app configuration. To resolve this, please contact our customer support team from either /feedback in your Slack workspace or https://my.slack.com/help/requests/new .

Lastly, if you don't have any particular reason to use Hubot, we highly recommend using a newer platform feature for new app development. Most of the things that Hubot w/ Slack adapter can be done with Bolt framework along with Socket Mode + Events API in a better way. Refer to the Getting Started Guide for learning how to use it.

I hope this was helpful to you and everything will work well for you soon.

[yihchu]

Hi @yihchu, I've checked your comment in #642 and tried to see the same situation on my end. However, my Hubot app does not miss any messages. Also, we do not see any outage / incident reports on the RTM API (= underlying WebSocket connectivity) at this moment.

The only possible cause that I can think of is that your Hubot app's WebSocket connection might be a bit unstable due to something specific to your network environment (or anything between Slack server and your Hubot app process). In this case, the Slack server-side could fail to occasionally send message events to your app.

To narrow the issue down, I would suggest trying to run the same app in a completely different setting (say, on a different cloud service) and see how it goes. If your situation persists regardless of where to run your Hubot app, something wrong may be happening to your workspace or Hubot app configuration. To resolve this, please contact our customer support team from either /feedback in your Slack workspace or https://my.slack.com/help/requests/new .

Lastly, if you don't have any particular reason to use Hubot, we highly recommend using a newer platform feature for new app development. Most of the things that Hubot w/ Slack adapter can be done with Bolt framework along with Socket Mode + Events API in a better way. Refer to the Getting Started Guide for learning how to use it.

I hope this was helpful to you and everything will work well for you soon.

@seratch Thanks. Could you tell me the ports that hubot uses.

[github-actions]

👋 It looks like this issue has been open for 30 days with no activity. We'll mark this as stale for now, and wait 10 days for an update or for further comment before closing this issue out. If you think this issue needs to be prioritized, please comment to get the thread going again! Maintainers also review issues marked as stale on a regular basis and comment or adjust status if the issue needs to be reprioritized.

[github-actions]

As this issue has been inactive for more than one month, we will be closing it. Thank you to all the participants! If you would like to raise a related issue, please create a new issue which includes your specific details and references this issue number.