-
-
Notifications
You must be signed in to change notification settings - Fork 80.7k
[Bug]: Silently lost connection to Slack #72808
Copy link
Copy link
Closed
Labels
P1High-priority user-facing bug, regression, or broken workflow.High-priority user-facing bug, regression, or broken workflow.bugSomething isn't workingSomething isn't workingbug:behaviorIncorrect behavior without a crashIncorrect behavior without a crashclawsweeper:linked-pr-openClawSweeper found an open linked pull request for this issue.ClawSweeper found an open linked pull request for this issue.clawsweeper:no-new-fix-prClawSweeper does not recommend queueing a new automated fix PR for this issue.ClawSweeper does not recommend queueing a new automated fix PR for this issue.clawsweeper:source-reproClawSweeper found a high-confidence source-level issue reproduction.ClawSweeper found a high-confidence source-level issue reproduction.impact:message-lossChannel message delivery can be lost, duplicated, or misrouted.Channel message delivery can be lost, duplicated, or misrouted.issue-rating: 🦞 diamond lobsterVery strong issue quality with high-confidence source-level or clear reproduction.Very strong issue quality with high-confidence source-level or clear reproduction.
Description
Metadata
Metadata
Assignees
Labels
P1High-priority user-facing bug, regression, or broken workflow.High-priority user-facing bug, regression, or broken workflow.bugSomething isn't workingSomething isn't workingbug:behaviorIncorrect behavior without a crashIncorrect behavior without a crashclawsweeper:linked-pr-openClawSweeper found an open linked pull request for this issue.ClawSweeper found an open linked pull request for this issue.clawsweeper:no-new-fix-prClawSweeper does not recommend queueing a new automated fix PR for this issue.ClawSweeper does not recommend queueing a new automated fix PR for this issue.clawsweeper:source-reproClawSweeper found a high-confidence source-level issue reproduction.ClawSweeper found a high-confidence source-level issue reproduction.impact:message-lossChannel message delivery can be lost, duplicated, or misrouted.Channel message delivery can be lost, duplicated, or misrouted.issue-rating: 🦞 diamond lobsterVery strong issue quality with high-confidence source-level or clear reproduction.Very strong issue quality with high-confidence source-level or clear reproduction.
Type
Fields
Priority
None yet
Bug type
Behavior bug (incorrect output/state without crash)
Beta release blocker
No
Summary
My slack connection to my openclaw had been working fine for several days. Today at lunch, I tried to demo to some friends and it never answered. Later when back at my desk, I sent more slack messages, and it still didn't answer. OTOH chatting through the web interface worked fine. Somehow the connection with Slack just silently stopped working.
Steps to reproduce
Expected behavior
It should reply over slack.
Actual behavior
It does not reply over slack.
OpenClaw version
v2026.4.19-beta.2
Operating system
macOS 26.2
Install method
I think npm, but I don't even remember for sure now.
Model
Qwen30b
Provider / routing chain
openclaw -> ollama -> quen
Additional provider/model setup details
No response
Logs, screenshots, and evidence
It shows the bot as "online" (green indicator):

but it ignores everything.
Impact and severity
Affected: Slack user
Severity: blocks workflow
Frequency: always (afaik)
Consequence: cannot use, since Slack is my only method of communication with the bot
Additional information
I haven't tried to fix it (eg, by restarting). If you give me hints on how to debug, I can upload any logs or dig into the root cause.