openclaw - 💡(How to fix) Fix exec approval followup dispatch fails with gateway timeout when user does not respond within approval window [1 comments, 2 participants]

Bug

When an exec command requires approval (allowlist mode) and the user does not respond within the approval window (~32min), the subsequent async followup dispatch times out after 60 seconds, failing to deliver the agent's response to the user's chat channel.

Evidence

From gateway logs (2026-04-04, user session: tide-pine/keen-pine):

00:05:38  [ws] res ✓ agent 53ms runId=exec-approval-followup:06336a4c-e260-41cc-820f-b45167515403
00:06:26  [ws] res ✓ exec.approval.waitDecision 1939120ms
00:06:43  exec approval followup dispatch failed (id=06336a4c-e260-41cc-820f-b45167515403): gateway timeout after 60000ms

Agent responded to the followup in 53ms (00:05:38), but the dispatch was marked failed 60 seconds later (00:06:43) with gateway timeout after 60000ms.

What Happened

1. User sent a command requiring exec approval → approval prompt shown
2. User did not approve within the timeout window
3. Gateway sent exec approval followup to agent ~32 min later
4. Agent responded in 53ms via WebSocket
5. But the followup dispatch still failed after 60s timeout

Expected Behavior

When the exec approval times out (user does not respond), the agent's followup response should be properly delivered to the user's chat channel (Feishu, etc.).

Actual Behavior

• Agent responds to the followup promptly (53ms)
• But the gateway's dispatch layer marks it as gateway timeout after 60000ms (60s)
• The agent's message never reaches the user's chat channel
• From the user's perspective, the agent suddenly goes silent, then later responds out of context

Environment

• OpenClaw: 2026.4.1 (da64a97)
• OS: Linux (WSL2, x86_64)
• Channel: Feishu (IM plugin)
• exec.host: gateway
• exec.security: allowlist
• exec.ask: on-miss

Reproduction

1. Configure exec with security: allowlist
2. Execute a command that triggers an approval prompt
3. Do NOT respond to the approval prompt (let it timeout)
4. Wait for the followup to trigger (~32min)
5. Observe: agent responds to the followup but the message is not delivered to the chat channel

Possible Cause

The async followup event may lack proper delivery routing context (e.g., Feishu channel + chat target) when it's triggered as an internal gateway event rather than a user-initiated message turn. The agent produces a response, but the dispatch layer cannot deliver it because:

• The original WebSocket connection/user context has timed out or been cleaned up
• The followup dispatch does not inherit the original delivery target (channel, chat_id, etc.)
• There may be a race condition where the agent's 53ms response arrives after the gateway has already moved on from the followup window