-
Notifications
You must be signed in to change notification settings - Fork 426
[ERROR] socket-mode:SocketModeClient:0 failed to send message on websocket: WebSocket is not open: #1428
Copy link
Copy link
Closed
Labels
auto-triage-staleneeds infoAn issue that is claimed to be a bug and hasn't been reproduced, or otherwise needs more infoAn issue that is claimed to be a bug and hasn't been reproduced, or otherwise needs more info
Description
Description
Follow on from Issue slackapi/node-slack-sdk#1471 .... Have upgraded following issue 1471, now receive this error after about 4-5 days of operation
[ERROR] socket-mode:SocketModeClient:0 failed to send message on websocket: WebSocket is not open: readyState 3 (CLOSED)
[ERROR] An unhandled error occurred while Bolt processed (type: event_callback, error: Error: Failed to send message on websocket: WebSocket is not open: readyState 3 (CLOSED))
What type of issue is this? (place an x in one of the [ ])
- [X ] bug
- enhancement (feature request)
- question
- documentation related
- example code related
- testing related
- discussion
Requirements (place an x in each of the [ ])
- [X ] I've read and understood the Contributing guidelines and have done my best effort to follow them.
- [X ] I've read and agree to the Code of Conduct.
- [ X] I've searched for any related issues and avoided creating a duplicate issue.
Bug Report
Filling out the following details about bugs will help us solve your issue sooner.
Reproducible in:
package version: npm '8.7.0'
node version: node '16.13.0'
OS version(s):FreeBSD 13.0-RELEASE-p11 (GENERIC) #0: Tue Apr 5 18:54:35 UTC 2022
npm list
[email protected] /usr/local/www/apache24/data/slack
├── @slack/[email protected]
├── @slack/[email protected]
├── @slack/[email protected]
├── @slack/[email protected]
├── @slack/[email protected]
├── @slack/[email protected]
├── @slack/[email protected]
├── @slack/[email protected]
├── @types/[email protected]
├── @types/[email protected]
├── @types/[email protected]
├── @types/[email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
└── [email protected]
Steps to reproduce:
- Intermittent issue ... process has been running for 4 days before error occurred.
Expected result:
Error handling to recover error, or how to deal with this error?
Actual result:
Process appeared to cease operation, although process remained running.
Attachments:
Logs, screenshots, screencast, sample project, funny gif, etc.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
auto-triage-staleneeds infoAn issue that is claimed to be a bug and hasn't been reproduced, or otherwise needs more infoAn issue that is claimed to be a bug and hasn't been reproduced, or otherwise needs more info