Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

socket-mode: a transient invalid_auth while reconnecting stops auto-reconnect permanently (no event emitted)

Aperta
  • Qualcosa non va?
#2,791 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
75/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
node.js, typescript
Ambito
backend, networking

Direzione di ricerca

Locate SocketModeClient and follow close → delayReconnectAttempt() → start() → retrieveWSSURL() to see where the rejected promise stops reconnection. Check the existing Socket Mode tests for initial-start and reconnect behavior, then add coverage for a transient invalid_auth during auto-reconnect and verify that retries continue or a disconnection/error event is emitted.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Description

After a Socket Mode connection closes, SocketModeClient stops reconnecting for good if a single apps.connections.open call returns invalid_auth (or another error the client treats as unrecoverable). The app stops receiving events, and nothing tells it so.

Slack sometimes returns invalid_auth temporarily during its own incidents. That makes a short Slack incident a permanent outage for the app until its process is restarted.

What happened

On 2026-10-22 at 16:08:41 UTC, during a period when Slack was returning HTTP 503s, two Socket Mode clients (two workspaces, two separate app tokens) reconnected at the same moment. Both got:

[ERROR] socket-mode:SocketModeClient:0 Failed to retrieve a new WSS URL (error: Error: An API error occurred: invalid_auth)
[ERROR] socket-mode:SocketModeClient:1 Failed to retrieve a new WSS URL (error: Error: An API error occurred: invalid_auth)
unhandled rejection {"code":"slack_webapi_platform_error","data":{"ok":false,"error":"invalid_auth"}}

After that, neither client made another attempt. No events arrived for 1h20. Restarting the process with the same tokens reconnected both clients immediately, so the tokens were never invalid.

Reproducible in
  • @slack/socket-mode 2.0.7 (through @slack/bolt 4.6). The same code is in 3.1.0.
  • Node 24.22
Code path
  1. The close listener calls this.delayReconnectAttempt(this.start) and doesn't handle the returned promise.
  2. start() calls retrieveWSSURL(). It classifies invalid_auth, not_authed, account_inactive, etc., and every RequestError and HTTPError, as unrecoverable, then rethrows instead of retrying.
  3. delayReconnectAttempt() runs cb.apply(this).then(res) with no rejection handler. The rejection is unhandled and the client never tries again. It emits no disconnected or error event, so the app can't detect the dead state.

The unrecoverable classification makes sense for the first start(), where the caller awaits it and can act on a bad token. It doesn't make sense on the auto-reconnect path, where no caller can see the error.

Suggested fix (any one of these)
  • While auto-reconnect is on, keep retrying unrecoverable errors in the reconnect path with backoff. A revoked token then shows up as repeated errors instead of silence.
  • Or emit an event when auto-reconnect gives up (State.Disconnected or an error), so apps can restart the client.
  • In either case, handle the promise in delayReconnectAttempt().

Related: #2656 (another unhandled rejection from the same delayReconnectAttempt path, triggered by a different race).

Lingua principale
TypeScript
Stelle
3.4k
Fork
691
Merge medio
1g 2h
PR unite (30g)
19

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di slackapi/node-slack-sdk

Tutte le issue di slackapi/node-slack-sdk

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.