Skip to content
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

Getting error "409 - Received an unexpected response for handshake" #1203

Closed
PrajwalNaik07 opened this issue Nov 18, 2024 · 3 comments
Closed
Labels
auto-triage-stale server-side Server-sider issue with the Slack Platform or Slack API

Comments

@PrajwalNaik07
Copy link

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

@seratch seratch added the server-side Server-sider issue with the Slack Platform or Slack API label Nov 19, 2024
@seratch
Copy link
Member

seratch commented Nov 19, 2024

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.

Copy link

👋 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.

Copy link

github-actions bot commented Jan 6, 2025

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.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jan 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
auto-triage-stale server-side Server-sider issue with the Slack Platform or Slack API
Projects
None yet
Development

No branches or pull requests

2 participants