Summary

In a Slack thread session, the agent produced a final answer in the session transcript, but the reply was not delivered to Slack. The session then remained stuck in processing, and a follow-up mention in the same Slack thread queued behind the stuck run, making the bot appear unresponsive.

This appears to be a delivery/session-finalization bug rather than a Slack permission issue: manual re-delivery of the already-generated final answer to the same thread succeeded.

Observed behavior

• Channel type: Slack thread
• Runtime: OpenClaw 2026.6.5
• The agent completed the investigation and generated a final answer in the session transcript.
• No Slack message was delivered for that final answer.
• The session was later reported as stalled with fields similar to:
  • state=processing
  • queueDepth=1
  • reason=active_work_without_progress
  • classification=stalled_agent_run
  • activeWorkKind=embedded_run
  • lastProgress=embedded_run:started
• A follow-up user mention in the same Slack thread did not get a response because it queued behind the stuck session.
• Manually posting the generated final answer to the same Slack thread worked, confirming Slack delivery/auth was functional.

Expected behavior

One of the following should happen after a final answer is generated:

1. The final answer is delivered to Slack and the session transitions to done.
2. If delivery fails, the failure is recorded explicitly and the session transitions to failed / recoverable state.
3. Follow-up messages in the same Slack thread are not blocked indefinitely behind a stalled completed answer.

Suggested safeguards

• Detect channel sessions stuck in processing after final-answer generation.
• If a final answer exists but no channel receipt exists, either retry delivery or mark the run failed with a clear delivery error.
• Ensure stalled embedded runs do not keep same-thread follow-up messages blocked indefinitely.

Privacy note

This report is intentionally sanitized. It does not include workspace URLs, channel IDs, thread IDs, customer identifiers, call IDs, phone numbers, internal tool output, or the original Slack transcript.