Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug]: Slack multi-workspace: outbound works on second workspace but inbound DM replies never reach OpenClaw [1 comments, 1 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#58523•Fetched 2026-04-08 02:01:38
View on GitHub
Comments
1
Participants
1
Timeline
3
Reactions
0
Author
david90232david90232
Participants
david90232david90232
Timeline (top)
labeled ×2commented ×1
  • I’m seeing a Slack multi-workspace issue where:
  • Workspace A works normally for inbound + outbound DMs
  • Workspace B can receive outbound messages from OpenClaw
  • but replies from Workspace B never make it back into OpenClaw
  • This persists even after verifying Slack app settings, refreshing tokens, and restarting the gateway.

Root Cause

  • I’m seeing a Slack multi-workspace issue where:
  • Workspace A works normally for inbound + outbound DMs
  • Workspace B can receive outbound messages from OpenClaw
  • but replies from Workspace B never make it back into OpenClaw
  • This persists even after verifying Slack app settings, refreshing tokens, and restarting the gateway.
RAW_BUFFERClick to expand / collapse

Bug type

Behavior bug (incorrect output/state without crash)

Beta release blocker

No

Summary

  • I’m seeing a Slack multi-workspace issue where:
  • Workspace A works normally for inbound + outbound DMs
  • Workspace B can receive outbound messages from OpenClaw
  • but replies from Workspace B never make it back into OpenClaw
  • This persists even after verifying Slack app settings, refreshing tokens, and restarting the gateway.

Steps to reproduce

  1. Configure OpenClaw with Slack in Socket Mode.
  2. Add two Slack workspaces as separate Slack accounts.
  3. Set session.dmScope to per-account-channel-peer.
  4. Add explicit bindings per Slack account.
  5. Verify both Slack accounts show healthy in openclaw status.
  6. Send a DM from Workspace A to the bot.
  7. Confirm Workspace A inbound + outbound works normally.
  8. Send an outbound message from OpenClaw to a user in Workspace B using the correct workspace-specific Slack user ID.
  9. Confirm the outbound message is delivered in Workspace B.
  10. Reply to that message from Workspace B.

Expected behavior

Replies from Workspace B should be received by OpenClaw, just like Workspace A, and continue the DM conversation normally.

Actual behavior

  • Workspace A works normally for inbound + outbound DMs.
  • Workspace B receives outbound messages from OpenClaw successfully.
  • Replies sent from Workspace B never arrive back in OpenClaw.
  • This persists even after:
    • refreshing bot/app tokens
    • restarting the gateway
    • verifying message.im
    • verifying im:history
    • comparing app settings/scopes/events/App Home against the working workspace
    • setting Workspace B as channels.slack.defaultAccount

OpenClaw version

2026.3.28

Operating system

macOS 26.3.1 (arm64)

Install method

No response

Model

openai-codex/gpt-5.4

Provider / routing chain

Slack (Socket Mode) → OpenClaw local gateway → main agent (gpt-5.4)

Additional provider/model setup details

  • Additional context
  • The same human user has different Slack user IDs in the two workspaces.
  • Outbound to Workspace B initially failed when using Workspace A’s user ID, but worked once the correct Workspace B user ID was used.
  • That suggests workspace-specific identity matters and may be related to inbound account/user/session resolution.
  • The Slack UI surface in Workspace B also appears different from Workspace A, looking more like an App Home / Chat / History interface with a “New Chat” button.

Environment

  • OpenClaw version: 2026.3.28
  • Slack mode: Socket Mode
  • Two Slack workspaces configured as separate Slack accounts
  • session.dmScope = per-account-channel-peer

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response

extent analysis

TL;DR

  • Verify the session.dmScope setting and ensure that the Slack user IDs used for outbound messages from OpenClaw match the expected IDs for each workspace, considering the workspace-specific identity.

Guidance

  • Review the session.dmScope setting to confirm it is correctly set to per-account-channel-peer for both workspaces.
  • Double-check that the correct Slack user IDs are used for outbound messages from OpenClaw to each workspace, taking into account the different user IDs for the same human user in different workspaces.
  • Investigate the differences in the Slack UI surface between Workspace A and Workspace B, potentially related to App Home or Chat/History interfaces, to understand if this affects inbound message handling.
  • Test sending replies from Workspace B using the Slack UI's "New Chat" button to see if this changes the behavior of inbound messages to OpenClaw.

Example

  • No specific code snippet can be provided without more details on the OpenClaw configuration or Slack API usage, but ensuring that the session.dmScope is correctly set and that workspace-specific user IDs are used for outbound messages is crucial.

Notes

  • The issue seems to be related to how OpenClaw resolves inbound account/user/session for Workspace B, potentially due to differences in Slack UI or user ID handling.
  • Further investigation into the Slack App settings, scopes, and events for both workspaces might provide more insights into why replies from Workspace B are not being received by OpenClaw.

Recommendation

  • Apply workaround: Verify and adjust the session.dmScope setting and ensure correct usage of workspace-specific Slack user IDs for outbound messages, as this seems to be the most direct approach to addressing the issue given the provided information.

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…

FAQ

Expected behavior

Replies from Workspace B should be received by OpenClaw, just like Workspace A, and continue the DM conversation normally.

#integration issue#index setup#retrieval issue#search optimization#API routing

Still need to ship something?

×6

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

Back to top recommendations

TRENDING