Socket Mode disconnection issue with the aiohttp-based client
See original GitHub issueHello, I’m following up after the issue #1065 and upgrading to Slack Bolt 1.8.
Shortly after upgrading, I experienced disconnections. This happened twice in the last 3 days - with the previous version the disconnection has happened every few weeks. What’s visible from my side is a Slack application still running, but unreachable through Slack slash commands. There are no logs related to the websocket, contrary to #1065. The bug symptoms are the same though, which makes me believe it’s related.
Reproducible in:
The Slack SDK version
slack-bolt==1.8.1
slack-sdk==3.10.1
slackclient==1.3.2
Python runtime version
Python 3.8.10
OS info
(running in a Docker container based on python:3.8.10-slim-buster
)
Steps to reproduce:
Run the app with socket mode for a few days.
Expected result:
The app is always reachable.
Actual result:
Slash commands or interacting with the app messages lead to the Slack error "/foo failed with the error "dispatch failed"
.
Thank you for your consideration!
Issue Analytics
- State:
- Created 2 years ago
- Comments:20 (10 by maintainers)
Hi @seratch , Apologies for getting back to you late. Thank you for the new releases, we’re now running
slack-bolt 1.9.2
andslack-sdk 3.11.2
. I’ll report back if any issue appears 😃That’s great to hear! Thanks for sharing the result 👍 Let me close this issue now.