-
Notifications
You must be signed in to change notification settings - Fork 380
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
too_many_websockets
causes Cannot read properties of undefined (reading 'event')
#2116
Comments
This should not be an error anymore in bolt v3.18 or newer. |
Thank you, any description link related to the fixed issue? |
Please upgrade the underlying |
Thank you, I'll upgrade the version! |
Sorry just saw this! @Ericxxt the following change in socket-mode 1.3.5 fixes the issue in this thread:
The details here are:
|
(Filling out the following with as much detail as you can provide will help us solve your issue sooner.)
@slack/bolt
version3.15.0
Refer to your
package.json
Your
App
and Receiver ConfigurationNode.js runtime version
v21.7.2
Steps to reproduce:
(Share the commands to run, source code, and project settings)
I just added a statement about
event.user === plan.operator
in current bolt app as below:It caused
But if I apply with
event!
, no such error forundefined (reading 'event')
produced nor too_many_websockets issueExpected result:
(Tell what you expected to happen)
Actual result:
(Tell what actually happened with logs, screenshots)
Requirements
For general questions/issues about Slack API platform or its server-side, could you submit questions at https://my.slack.com/help/requests/new instead. 🙇
Please read the Contributing guidelines and Code of Conduct before creating this issue or pull request. By submitting, you are agreeing to those rules.
The text was updated successfully, but these errors were encountered: