openclaw - 💡(How to fix) Fix [Bug]: 2026.4.24 regression — Discord exec approval no longer sends interactive prompt via DM; approval callbacks loop with repeated errors after user approves [1 comments, 2 participants]

Bug Summary

Two related regressions in OpenClaw 2026.4.24 affecting Discord exec approval flow:

1. Approval prompts no longer appear in Discord DM — Before upgrading, exec approval requests were sent as interactive Discord messages (with Allow/Deny buttons) via DM. After upgrading to 2026.4.24, approval prompts only appear in the Web UI. No config changes were made.

2. After approving in Discord (when prompt does appear), repeated error messages are sent — If an approval prompt does surface in Discord and the user clicks Allow, the system keeps sending repeated error messages about that same approval instead of recognizing it was already processed.

Reproduction Steps

Issue 1: No Discord DM approval prompt

1. Have execApprovals enabled for Discord account
2. Trigger a command that requires exec approval
3. Observe: approval prompt only appears in Web UI, not in Discord DM
4. Previous version correctly sent interactive approval card via Discord DM

Issue 2: Repeated approval errors

1. When an approval prompt does appear in Discord (e.g., in channel)
2. Click Allow
3. The command executes, but repeated error messages about the same approval keep appearing in the channel
4. Errors indicate the approval callback is being re-processed or the approval result was lost

Environment

• OpenClaw version: 2026.4.24 (upgraded from previous stable)
• Platform: macOS Apple Silicon (Darwin 25.4.0)
• Node.js: v22.22.0
• Channel: Discord
• No configuration changes were made between versions
• Previous version did NOT have this issue

Root Cause Analysis

• The Discord interactive component registration (inline buttons for approval) may have changed or broken in 2026.4.24, causing the system to fall back to Web UI-only delivery
• The approval lifecycle callback in Discord appears to have a race condition with the message queue (collect/steer mode), causing the approval result to not properly terminate the flow
• This may be related to the ENOTEMPTY bug (#71802) — if bundled plugin loading fails, Discord interactive capabilities may not fully initialize

Related Issues

• #58769 — excessive exec approval prompts regression (2026.3.31)
• #32062 — exec approval lifecycle outcomes delayed by collect/steer queueing
• #46708 — exec approval UX can fail across Web UI / TUI
• #71802 — ENOTEMPTY on bundled plugin-sdk (same version, may be related)

Workaround

Disable exec approvals for Discord:

channels:
  discord:
    accounts:
      ai-expert:
        execApprovals:
          enabled: false

This eliminates both the missing prompt and the repeated error issues, at the cost of losing the approval gate for exec commands.