Fix: Discord Messages Lost After WebSocket Reconnect

Discord's Gateway uses sequence numbers (s field) to track every event. After a disconnect, you have a short window to resume the session with the last known s value. If OpenClaw starts a fresh session instead of resuming, Discord does not send the events from the gap — those @mentions are gone.

What You See in Logs

The key line is session resumed? false. When this appears, Discord treated the reconnect as a new session and the sequence gap is unrecoverable. Events from the disconnection window are lost.

Fix A: Enable Session Resume

OpenClaw supports Discord Gateway session resume. Make sure it's enabled in your config and that the resume URL is being stored between restarts:

{
  "channels": {
    "discord": {
      "gateway": {
        "resumeOnReconnect": true,
        "storeSessionState": true
      }
    }
  }
}

After updating config, restart and check logs for confirmation:

openclaw gateway restart && openclaw logs --follow | grep -i 'discord\\|resume\\|session'

You should see [discord] session resume available: true and after any reconnect: session resumed? true.

Fix B: Shorten the Reconnect Window

Discord only holds session state for approximately 60 seconds after a disconnect. If your gateway takes longer than that to reconnect, resume will fail even if it's enabled. Common causes of slow reconnects:

Fix C: Use Discord Gateway v10

Older gateway versions have weaker resume support. Gateway v10 has more reliable resume behavior and better handling of the RECONNECT opcode. Check which version OpenClaw is using and upgrade if needed:

{
  "channels": {
    "discord": {
      "gateway": {
        "version": 10
      }
    }
  }
}

Monitor for Disconnects

To see when disconnects happen and whether resumes succeed:

openclaw logs --follow | grep -E '(1006|1005|disconnect|resume|reconnect)'

Still Missing Messages?

If messages are still being lost even after enabling resume, run the Doctor for a full channel diagnostic: