Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix Slack socket mode fails with "reserved redaction sentinel" error despite valid tokens — infinite restart loop [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#59945•Fetched 2026-04-08 02:38:27
View on GitHub
Comments
1
Participants
2
Timeline
1
Reactions
0
Author
MarkkayTavionMarkkayTavion
Participants
GMTekAIGMTekAIMarkkayTavionMarkkayTavion
Timeline (top)
commented ×1

Slack channel fails to connect in socket mode with valid tokens. Gateway enters infinite restart loop with reserved redaction sentinel "__OPENCLAW_REDACTED__" is not valid config data error.

Error Message

Full restart loop pattern in ~/.openclaw/logs/gateway.log.

Root Cause

Slack channel fails to connect in socket mode with valid tokens. Gateway enters infinite restart loop with reserved redaction sentinel "__OPENCLAW_REDACTED__" is not valid config data error.

Fix Action

Workaround

Use Hermes agent (separate deployment) — Slack works fine there.

Code Example

"slack": {
  "enabled": true,
  "botToken": "xoxb-...",
  "appToken": "xapp-...",
  "mode": "socket",
  "groupPolicy": "allowlist",
  "nativeStreaming": true,
  "allowFrom": ["U0AQ9DXKKJA"]
}

---

slack: Reserved redaction sentinel "__OPENCLAW_REDACTED__" is not valid config data
slack: Starting provider... (restarts continuously)

---

curl -s https://slack.com/api/apps.connections.open \
  -H "Authorization: Bearer $APP_TOKEN" \
  -X POST
# Returns: {"ok":true,"url":"wss://..."}
RAW_BUFFERClick to expand / collapse

Summary

Slack channel fails to connect in socket mode with valid tokens. Gateway enters infinite restart loop with reserved redaction sentinel "__OPENCLAW_REDACTED__" is not valid config data error.

Environment

  • OpenClaw version: 2026.4.2 (d74a122)
  • OS: macOS 15.4 (arm64)
  • Node: v25.8.2
  • Slack plugin: @openclaw/slack (latest)

Configuration

"slack": {
  "enabled": true,
  "botToken": "xoxb-...",
  "appToken": "xapp-...",
  "mode": "socket",
  "groupPolicy": "allowlist",
  "nativeStreaming": true,
  "allowFrom": ["U0AQ9DXKKJA"]
}

Steps to Reproduce

  1. Configure Slack with valid tokens
  2. Enable Slack channel
  3. Restart gateway
  4. Observe infinite restart loop

Expected Behavior

Slack connects via socket mode and receives messages.

Actual Behavior

Gateway logs show:

slack: Reserved redaction sentinel "__OPENCLAW_REDACTED__" is not valid config data
slack: Starting provider... (restarts continuously)

Verification

Tokens verified working via direct API test:

curl -s https://slack.com/api/apps.connections.open \
  -H "Authorization: Bearer $APP_TOKEN" \
  -X POST
# Returns: {"ok":true,"url":"wss://..."}

Bot token also valid via auth.test.

Logs

Full restart loop pattern in ~/.openclaw/logs/gateway.log.

Workaround

Use Hermes agent (separate deployment) — Slack works fine there.

Related

Possibly related to exec-approval token redaction introduced in recent versions.

extent analysis

TL;DR

The issue can be likely resolved by adjusting the Slack configuration to properly handle the reserved redaction sentinel or by temporarily reverting the recent changes related to exec-approval token redaction.

Guidance

  • Review the recent changes introduced in OpenClaw version 2026.4.2, specifically the exec-approval token redaction, to understand how it affects the Slack configuration.
  • Verify that the botToken and appToken are correctly formatted and not accidentally including the reserved redaction sentinel __OPENCLAW_REDACTED__.
  • Consider temporarily disabling the nativeStreaming option to see if it resolves the infinite restart loop issue.
  • Check the OpenClaw documentation for any specific guidelines on configuring Slack with socket mode and token redaction.

Example

No code snippet is provided as the issue seems to be related to configuration and token handling rather than code implementation.

Notes

The issue might be specific to the combination of OpenClaw version, Slack plugin, and macOS environment. Further investigation into the exec-approval token redaction changes and their impact on Slack configuration is necessary.

Recommendation

Apply workaround: Use the Hermes agent as a temporary solution until the root cause of the issue is identified and resolved, as it has been reported to work fine with Slack.

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#prompt template#agent execution#callback error#memory management

Still need to ship something?

×6

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

Back to top recommendations

TRENDING