Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix Slack Socket Mode: expose clientPingTimeout config to prevent false disconnects on high-latency networks [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#74590•Fetched 2026-04-30 06:22:32
View on GitHub
Comments
1
Participants
2
Timeline
3
Reactions
2
Author
redasadkiredasadki
Participants
clawsweeper[bot]clawsweeper[bot]redasadkiredasadki
Timeline (top)
closed ×1commented ×1cross-referenced ×1

Fix Action

Workaround

None currently. The health monitor's only config is enabled: boolean — no timeout tuning available.

Code Example

grep -c "pong wasn't received" /tmp/openclaw/openclaw-2026-04-29.log
→ 1175

grep -c "slack socket disconnected" /tmp/openclaw/openclaw-2026-04-29.log
→ 211

grep -c "slack socket mode connected" /tmp/openclaw/openclaw-2026-04-29.log
→ 214

---

{
  channels: {
    slack: {
      socketMode: {
        clientPingTimeout: 20000,  // default: 5000 (from @slack/socket-mode SDK)
        serverPingTimeout: 30000,  // default: 30000
      }
    }
  }
}
RAW_BUFFERClick to expand / collapse

Problem

The Slack Socket Mode SDK's default clientPingTimeout of 5000ms causes constant false disconnects on networks with any WebSocket latency jitter. On our setup (Mac Mini, ISP connection via 8.8.8.8/1.1.1.1 DNS), we see:

  • 211 disconnects and 1175 pong timeout warnings in a single day
  • Pattern: connect → ~30-45s → "A pong wasn't received from the server before the timeout of 5000ms!" → disconnect → reconnect in 2s → repeat
  • HTTP to slack.com works fine (200 in 0.77s) — only WebSocket keepalives are affected
  • Messages ARE delivered during the brief connected windows, but the cycling is noisy and occasionally drops messages during the ~2s reconnect gap

This is the same issue as slackapi/bolt-js#2496 (open since Apr 2025, labeled server-side-issue).

Environment

  • OpenClaw 2026.4.26 (latest)
  • macOS 26.4.1 (arm64), Node 25.9.0
  • Slack channel mode: socket (default)

Evidence

grep -c "pong wasn't received" /tmp/openclaw/openclaw-2026-04-29.log
→ 1175

grep -c "slack socket disconnected" /tmp/openclaw/openclaw-2026-04-29.log
→ 211

grep -c "slack socket mode connected" /tmp/openclaw/openclaw-2026-04-29.log
→ 214

Proposal

Expose clientPingTimeout and serverPingTimeout as config keys under channels.slack, e.g.:

{
  channels: {
    slack: {
      socketMode: {
        clientPingTimeout: 20000,  // default: 5000 (from @slack/socket-mode SDK)
        serverPingTimeout: 30000,  // default: 30000
      }
    }
  }
}

These map directly to @slack/socket-mode SocketModeOptions clientPingTimeout and serverPingTimeout.

The current 5000ms default is too aggressive for many real-world networks. A user-configurable timeout (e.g., 15-20s) would eliminate false disconnects without any other changes.

Workaround

None currently. The health monitor's only config is enabled: boolean — no timeout tuning available.

extent analysis

TL;DR

Increase the clientPingTimeout value to a higher setting, such as 15-20 seconds, to reduce false disconnects due to network latency jitter.

Guidance

  • Review the proposed configuration change to expose clientPingTimeout and serverPingTimeout as config keys under channels.slack to allow for user-configurable timeouts.
  • Consider increasing the clientPingTimeout value to a setting that balances the need to detect genuine disconnects with the need to accommodate network latency jitter.
  • Verify the effectiveness of the increased timeout by monitoring the number of disconnects and pong timeout warnings.
  • If possible, test the proposed configuration change in a controlled environment before implementing it in production.

Example

{
  channels: {
    slack: {
      socketMode: {
        clientPingTimeout: 20000,  // increased from default 5000
        serverPingTimeout: 30000,  // default value
      }
    }
  }
}

Notes

The ideal clientPingTimeout value may vary depending on the specific network environment and requirements. Further testing and monitoring may be necessary to determine the optimal setting.

Recommendation

Apply the proposed configuration change to increase the clientPingTimeout value, as it is a targeted solution that addresses the root cause of the issue without introducing significant changes or risks.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#tokenizer error#prompt formatting#chain error#conversation history

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix Slack Socket Mode: expose clientPingTimeout config to prevent false disconnects on high-latency networks [1 comments, 2 participants]