openclaw - 💡(How to fix) Fix Slack explicit mentions need visible fallback on handler timeout

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…

Error Message

  • Original handler error behavior is preserved for diagnostics/status handling.

Root Cause

  • Only explicit human room/channel Slack mentions receive this fallback.
  • Bot-authored messages and non-explicit room messages do not get fallback posts.
  • Fallback is sent only when no prior visible reply/tool output was delivered.
  • Fallback is deduped by account, agent, Slack channel, and Slack message timestamp.
  • Original handler error behavior is preserved for diagnostics/status handling.
  • No automatic retry is added in this slice because the timed-out handler may already have side effects in flight.

Fix Action

Fix / Workaround

Focused Slack dispatch tests plus whitespace/format checks.

RAW_BUFFERClick to expand / collapse

Problem

An explicit human Slack mention can route into OpenClaw successfully, then the Codex/app-server handler can time out before producing assistant text, tool output, or any other visible reply. From Slack, that looks like a silent routing failure.

Acceptance criteria

  • Only explicit human room/channel Slack mentions receive this fallback.
  • Bot-authored messages and non-explicit room messages do not get fallback posts.
  • Fallback is sent only when no prior visible reply/tool output was delivered.
  • Fallback is deduped by account, agent, Slack channel, and Slack message timestamp.
  • Original handler error behavior is preserved for diagnostics/status handling.
  • No automatic retry is added in this slice because the timed-out handler may already have side effects in flight.

Validation target

Focused Slack dispatch tests plus whitespace/format checks.

Related: #44925, #58519.

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…

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 explicit mentions need visible fallback on handler timeout