#slack crashing gateway

1 messages · Page 1 of 1 (latest)

rose wadi
#

Any one (except me) have a problem whenever someone write to OC it crashes the gateway?

log:

[WARN]  socket-mode:SlackWebSocket:19 A pong wasn't received from the server before the timeout of 5000ms!
slack socket disconnected (disconnect). retry 1/12 in 2s
slack socket mode connected
{
  "type": "oauth"
}
[WARN]  socket-mode:SlackWebSocket:20 A pong wasn't received from the server before the timeout of 5000ms!
handshake timeout conn=ad9ef840-f95c-4fab-a89b-07ef79695094 peer=127.0.0.1:59880->127.0.0.1:18789 remote=127.0.0.1
{
  "cause": "handshake-timeout",
  "handshake": "failed",
  "durationMs": 14496,
  "lastFrameType": "req",
  "lastFrameMethod": "connect",
  "lastFrameId": "587d5d05-e468-4e56-afc5-79ea758d27ae",
  "host": "127.0.0.1:18789",
  "remoteAddr": "127.0.0.1",
  "remotePort": 59880,
  "localAddr": "127.0.0.1",
  "localPort": 18789,
  "endpoint": "127.0.0.1:59880->127.0.0.1:18789",
  "handshakeMs": 14426
}
gateway connect failed: Error: gateway closed (1000):
gateway connect failed: Error: gateway closed (1000):
⇄ res ✓ sessions.list 55ms conn=24409ce3…ea07 id=866541b8…6173
slack socket disconnected (disconnect). retry 1/12 in 2s
slack socket mode connected
⇄ res ✓ sessions.list 73ms conn=24409ce3…ea07 id=98d58572…3c90
[tools] message failed: An API error occurred: not_in_channel raw_params={"action":"read","channel":"slack","target":"C041MUFT0HW","limit":50}
[tools] message failed: An API error occurred: not_in_channel raw_params={"action":"read","channel":"slack","target":"C041MUFT0HW","limit":50}
ignoring unprofiled safeBins entries (python3); use allowlist or define tools.exec.safeBinProfiles.<bin>
interpreter/runtime binaries in safeBins (python3) are unsafe without explicit hardened profiles; prefer allowlist entries
delivered reply to channel:D0AFRMMGKRD
delivered reply to channel:D0AFRMMGKRD
{
  "type": "oauth"
}
hushed wolfBOT
#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

rose wadi
#

this happens after the update! 2026.4.25

cunning ermineBOT
#

First thing: what OpenClaw version are you on?

openclaw --version

From that log, the most suspicious line is:

message failed: ... not_in_channel ... target:"C041MUFT0HW"

That usually means the Slack app/bot is trying to read a channel it is not a member of or doesn’t have the right Slack scopes for.

Try these in order:

# 
openclaw status --all
openclaw channels status --probe
openclaw doctor

Then in Slack, make sure the OpenClaw app is actually added to that channel:

/invite @OpenClaw

For private channels, add the app manually in Slack’s channel integrations.

Also verify the Slack app manifest/scopes include the channel history scopes and reinstall the Slack app after changing scopes. Docs: https://docs.openclaw.ai/channels/slack

The pong wasn't received / socket reconnect can happen if the gateway is busy, wedged, or restarting, but not_in_channel is a concrete permissions clue. If it truly exits/crashes, paste:

#
  1. openclaw --version
  2. the 30–60 log lines before the actual process exit
  3. sanitized channels.slack config, no tokens

If it’s reproducible on current OpenClaw, that’s probably worth a GitHub issue too: https://github.com/openclaw/openclaw/issues 🦐

#

Please don’t post obfuscated invite links here.

Keeping this thread for the Slack gateway crash. If you have an OpenClaw issue, share the version/logs here or file it at https://github.com/openclaw/openclaw/issues.

#

Ah — 2026.4.25 is a useful clue. I’d treat this as likely update/regression-ish, especially with the Slack socket reconnect + gateway handshake timeout combo.

First get off .25 if possible:

openclaw update
openclaw doctor --fix
openclaw gateway restart
openclaw status --all
openclaw channels status --probe

The changelog has 2026.4.26 with update/install hardening, so .25 may have left you with mixed/stale plugin/runtime bits.

Separate issue: this line still means Slack permissions/channel membership are wrong:

# 
not_in_channel ... target:"C041MUFT0HW"

Make sure the Slack app is actually added to that channel (/invite @OpenClaw) and reinstall the Slack app if you changed scopes. Slack docs: https://docs.openclaw.ai/channels/slack

The safeBins python3 warning is unrelated to the crash; clean it up later by removing python3 from tools.exec.safeBins.

If it still crashes on latest after doctor --fix, please file this with the full pre-crash logs: https://github.com/openclaw/openclaw/issues

#

Small correction: OpenClaw support should stay in this #help thread or go to the official GitHub issues page: https://github.com/openclaw/openclaw/issues

Please don’t move people to DMs, “support tickets,” or unofficial invite links. Public threads help others find the fix later via Answer Overflow.

rose wadi
#

it s after upgrade

2026.4.25

cunning ermineBOT
#

Yep, that lines up with a .25 upgrade issue. I just re-checked current changelog: 2026.4.26 includes update/runtime fixes around mixed stale installs and 1006/disconnect cascades, so I would not debug .25 deeply yet.

Do this first:

openclaw update
openclaw --version
openclaw doctor --fix
openclaw gateway restart
openclaw status --all
openclaw channels status --probe

If openclaw --version still says 2026.4.25, the update didn’t actually swap cleanly.

Two separate signals in your log:

#
  • not_in_channel = Slack app isn’t in channel C041MUFT0HW or lacks scopes. Invite the app to that Slack channel / reinstall Slack app after scope changes.
  • socket pong + gateway handshake timeout after upgrade = likely the .25/stale runtime problem. Get to .26+ first.

If it still crashes on .26+, please file a GitHub issue with openclaw --version, openclaw status --all, and the 50 lines before the exit: https://github.com/openclaw/openclaw/issues

rose wadi
#

upgrading to newer version solved it for me!