"too_many_websockets" error

[Dana-Engel]

I use the Slack/bolt SDK in my slackbot for a while now. In the past 10 weeks we experience an odd behavior of the slackbot, when using the slash command in slack it sometimes open the modal and sometimes not with a 'dispatch_failed' error. When it doesn't work we get this error on the slackbot's pod:

2023-12-18 00:32:54:634 debug: Transitioning to state: connecting:authenticated {}
2023-12-18 00:32:54:647 debug: Transitioning to state: connecting:handshaking {}
2023-12-18 00:32:54:657 debug: Received a message on the WebSocket: {"type":"disconnect","reason":"too_many_websockets","debug_info":{"host":"applink-11"}} {}
2023-12-18 00:32:54:657 error: An unhandled error occurred while Bolt processed (type: undefined, error: TypeError: Cannot read properties of undefined (reading 'event')) {}
2023-12-18 00:32:54:657 debug: Error details: TypeError: Cannot read properties of undefined (reading 'event'), retry num: undefined, retry reason: undefined {}

We don't actively open web sockets in our code, we only use the slack/bolt SDK that manages it for us.

We tried to update the SDK's version, downgrade it, nothing worked (the versions I tried are: 3.17.0, 3.16.0, 3.15.0, 3.13.2, 3.12.1, 3.8.1).

Thank you in advance for trying to help me solve this issue

[seratch]

Sorry for our slow response here. The error can be raised when your app has more than 10 WebSocket connections for some reason. If you're still experiencing this, please consider revoking the app-level token and start a fresh connection with a new token.

[github-actions[bot]]

👋 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[bot]]

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.