You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have created a slack bot in GCP Kubernetes environment. The bot is written in bolt python and uses socket mode. We are running 10 pods simultaneously. Lately, we are facing the following issue -
Received an unexpected response for handshake (status: 409, response: HTTP/1.1 409 Conflict
via: envoy-wss-iad-txewoffa
date: Tue, 05 Nov 2024 19:55:36 GMT
server: envoy
connection: close
content-length: 0, session id: 6414fcdf-e0c8-4cc3-913b-94e05d6f2904)
Could you help me understand what the issue is and how to resolve it
The text was updated successfully, but these errors were encountered:
Hi @PrajwalNaik07, thanks for taking the time to report this. This is a known issue on the API server side, and this is the latest status: slackapi/node-slack-sdk#2094 (comment) Please subscribe to the issue thread to receive more updates to come.
👋 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.
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.
I have created a slack bot in GCP Kubernetes environment. The bot is written in bolt python and uses socket mode. We are running 10 pods simultaneously. Lately, we are facing the following issue -
Could you help me understand what the issue is and how to resolve it
The text was updated successfully, but these errors were encountered: