Bug Description

Discord ackReaction (👀) stopped working in guild channels after upgrading to v2026.4.27. The reaction never fires — no logs or errors related to ackReaction appear in gateway logs.

Environment

• OpenClaw version: 2026.4.27
• Channel: Discord (guild/channel)
• Config: ackReaction: "👀", ackReactionScope: "all" (both at channels.discord and messages level)
• Manual reactions via message(action=react) work fine
• groupPolicy: "open"
• Guild config has per-channel users allowlist

Logs

[discord] channel resolve failed; using config entries. fetch failed | Client network socket disconnected before secure TLS connection was established

No ackReaction-related log entries at all — the feature appears to be skipped entirely.

Suspected Cause

Changelog fix #73133: "skip reaction events before REST channel fetch when notifications are off, guild reactions are disabled, or allowlist mode cannot match without channel overrides" — the "channel resolve failed" path likely causes ackReaction to be skipped entirely.

Config

{
  "channels.discord.ackReaction": "👀",
  "channels.discord.ackReactionScope": "all",
  "channels.discord.groupPolicy": "open",
  "channels.discord.guilds": {
    "<guild_id>": {
      "requireMention": false,
      "channels": {
        "<channel_id>": { "users": ["<user_id>"] }
      }
    }
  }
}

Workaround

No known workaround. Manual message(action=react, emoji="👀") works, but automatic ackReaction on inbound messages does not fire.