Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug]: Discord DM heartbeats erroneously resolve `user:<snowflake>` to `channel:<snowflake>` [1 comments, 2 participants]

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…
GitHub stats
openclaw/openclaw#75359•Fetched 2026-05-02 05:35:38
View on GitHub
Comments
1
Participants
2
Timeline
8
Reactions
2
Author
luna-systemluna-system
Participants
clawsweeper[bot]clawsweeper[bot]luna-systemluna-system
Timeline (top)
labeled ×2mentioned ×2subscribed ×2closed ×1

Heartbeat messages targeting discord DMs fail permanently. Attached is a full bug report generated by kimi-code (who found the bug as well).

openclaw-discord-dm-heartbeat-bug-report.md

Error Message

"Unknown Channel" error in heartbeat logs {"0":"{"subsystem":"gateway/heartbeat"}","1":{"error":"Unknown Channel"},"2":"heartbeat failed: Unknown Channel","meta":{"runtime":"node","runtimeVersion":"24.14.1","hostname":"unknown","name":"{"subsystem":"gateway/heartbeat"}","parentNames":["openclaw"],"date":"2026-04-30T22:33:09.804Z","logLevelId":5,"logLevelName":"ERROR","path":{"fullFilePath":"file:///home/luna/.npm-global/lib/node_modules/openclaw/dist/subsystem-CWI_MDy.js:336:51","fileName":"subsystem-CWI_MDy_.js","fileNameWithLine":"subsystem-CWI_MDy_.js:336","fileColumn":"51","fileLine":"336","filePath":".npm-global/lib/node_modules/openclaw/dist/subsystem-CWI_MDy_.js","filePathWithLine":".npm-global/lib/node_modules/openclaw/dist/subsystem-CWI_MDy_.js:336","method":"logToFile"}},"time":"2026-04-30T17:33:09.804-05:00"} {"0":"{"subsystem":"gateway/delivery-recovery"}","1":"Retry failed for delivery 6731ca8c-d4be-4aa0-8ce2-603e77fbdd18: Unknown Channel","meta":{"runtime":"node","runtimeVersion":"24.14.1","hostname":"unknown","name":"{"subsystem":"gateway/delivery-recovery"}","parentNames":["openclaw"],"date":"2026-05-01T00:50:03.347Z","logLevelId":4,"logLevelName":"WARN","path":{"fullFilePath":"file:///home/luna/.npm-global/lib/node_modules/openclaw/dist/subsystem-CWI_MDy.js:337:14","fileName":"subsystem-CWI_MDy_.js","fileNameWithLine":"subsystem-CWI_MDy_.js:337","fileColumn":"14","fileLine":"337","filePath":".npm-global/lib/node_modules/openclaw/dist/subsystem-CWI_MDy_.js","filePathWithLine":".npm-global/lib/node_modules/openclaw/dist/subsystem-CWI_MDy_.js:337","method":"logToFile"}},"time":"2026-04-30T19:50:03.347-05:00"}

Root Cause

Heartbeat messages targeting discord DMs fail permanently. Attached is a full bug report generated by kimi-code (who found the bug as well).

openclaw-discord-dm-heartbeat-bug-report.md

Code Example

{"0":"{\"subsystem\":\"gateway/heartbeat\"}","1":{"error":"Unknown Channel"},"2":"heartbeat failed: Unknown Channel","_meta":{"runtime":"node","runtimeVersion":"24.14.1","hostname":"unknown","name":"{\"subsystem\":\"gateway/heartbeat\"}","parentNames":["openclaw"],"date":"2026-04-30T22:33:09.804Z","logLevelId":5,"logLevelName":"ERROR","path":{"fullFilePath":"file:///home/luna/.npm-global/lib/node_modules/openclaw/dist/subsystem-CWI_MDy_.js:336:51","fileName":"subsystem-CWI_MDy_.js","fileNameWithLine":"subsystem-CWI_MDy_.js:336","fileColumn":"51","fileLine":"336","filePath":".npm-global/lib/node_modules/openclaw/dist/subsystem-CWI_MDy_.js","filePathWithLine":".npm-global/lib/node_modules/openclaw/dist/subsystem-CWI_MDy_.js:336","method":"logToFile"}},"time":"2026-04-30T17:33:09.804-05:00"}
{"0":"{\"subsystem\":\"gateway/delivery-recovery\"}","1":"Retry failed for delivery 6731ca8c-d4be-4aa0-8ce2-603e77fbdd18: Unknown Channel","_meta":{"runtime":"node","runtimeVersion":"24.14.1","hostname":"unknown","name":"{\"subsystem\":\"gateway/delivery-recovery\"}","parentNames":["openclaw"],"date":"2026-05-01T00:50:03.347Z","logLevelId":4,"logLevelName":"WARN","path":{"fullFilePath":"file:///home/luna/.npm-global/lib/node_modules/openclaw/dist/subsystem-CWI_MDy_.js:337:14","fileName":"subsystem-CWI_MDy_.js","fileNameWithLine":"subsystem-CWI_MDy_.js:337","fileColumn":"14","fileLine":"337","filePath":".npm-global/lib/node_modules/openclaw/dist/subsystem-CWI_MDy_.js","filePathWithLine":".npm-global/lib/node_modules/openclaw/dist/subsystem-CWI_MDy_.js:337","method":"logToFile"}},"time":"2026-04-30T19:50:03.347-05:00"}

---

function parseDiscordExplicitTarget(raw) {
      try {
          const target = parseDiscordTarget(raw, { defaultKind: "channel" });
          if (!target) return null;
          return {
-             to: target.id,
+             to: target.normalized,
              chatType: target.kind === "user" ? "direct" : "channel"
          };
      } catch {
          return null;
      }
  }
RAW_BUFFERClick to expand / collapse

Bug type

Behavior bug (incorrect output/state without crash)

Beta release blocker

No

Summary

Heartbeat messages targeting discord DMs fail permanently. Attached is a full bug report generated by kimi-code (who found the bug as well).

openclaw-discord-dm-heartbeat-bug-report.md

Steps to reproduce

  1. With agents.list.<id>.heartbeat
    • Set target to "discord"
    • Set to to "user:<user snowflake>"
    • Set directPolicy to "allow" **
    • Set accountId to explicit channels Id **
  2. With channels.discord
    • Set showAlerts, useIndicator, and showOk to true **
  3. Set explicit allowFrom for agents in channels **
  4. Wait for or trigger a heartbeat

** these may not matter here and were set explicitly as part of troubleshooting this bug. these agents have already been successfully paired, so allowFrom shouldn't be necessary, and indeed it's not necessary for an identical config for Telegram.

Expected behavior

Heartbeat message should be delivered to Discord DMs. Note that our configuration explicitly has all heartbeat messages enabled for discord.

Actual behavior

"Unknown Channel" error in heartbeat logs Permafailure state of messages in delivery-queue, due to to field being clobbered into channel:<my user snowflake>

OpenClaw version

2026.4.24

Operating system

arch

Install method

npm global

Model

kimi-code/kimi-for-coding

Provider / routing chain

openclaw->kimi-code->kimi-for-coding

Additional provider/model setup details

No response

Logs, screenshots, and evidence

{"0":"{\"subsystem\":\"gateway/heartbeat\"}","1":{"error":"Unknown Channel"},"2":"heartbeat failed: Unknown Channel","_meta":{"runtime":"node","runtimeVersion":"24.14.1","hostname":"unknown","name":"{\"subsystem\":\"gateway/heartbeat\"}","parentNames":["openclaw"],"date":"2026-04-30T22:33:09.804Z","logLevelId":5,"logLevelName":"ERROR","path":{"fullFilePath":"file:///home/luna/.npm-global/lib/node_modules/openclaw/dist/subsystem-CWI_MDy_.js:336:51","fileName":"subsystem-CWI_MDy_.js","fileNameWithLine":"subsystem-CWI_MDy_.js:336","fileColumn":"51","fileLine":"336","filePath":".npm-global/lib/node_modules/openclaw/dist/subsystem-CWI_MDy_.js","filePathWithLine":".npm-global/lib/node_modules/openclaw/dist/subsystem-CWI_MDy_.js:336","method":"logToFile"}},"time":"2026-04-30T17:33:09.804-05:00"}
{"0":"{\"subsystem\":\"gateway/delivery-recovery\"}","1":"Retry failed for delivery 6731ca8c-d4be-4aa0-8ce2-603e77fbdd18: Unknown Channel","_meta":{"runtime":"node","runtimeVersion":"24.14.1","hostname":"unknown","name":"{\"subsystem\":\"gateway/delivery-recovery\"}","parentNames":["openclaw"],"date":"2026-05-01T00:50:03.347Z","logLevelId":4,"logLevelName":"WARN","path":{"fullFilePath":"file:///home/luna/.npm-global/lib/node_modules/openclaw/dist/subsystem-CWI_MDy_.js:337:14","fileName":"subsystem-CWI_MDy_.js","fileNameWithLine":"subsystem-CWI_MDy_.js:337","fileColumn":"14","fileLine":"337","filePath":".npm-global/lib/node_modules/openclaw/dist/subsystem-CWI_MDy_.js","filePathWithLine":".npm-global/lib/node_modules/openclaw/dist/subsystem-CWI_MDy_.js:337","method":"logToFile"}},"time":"2026-04-30T19:50:03.347-05:00"}

Impact and severity

Severity: Very High Frequency: Always Consequence: Agent alerts sent to the user are never delivered and fail permanently

Additional information

The kimi-code agent that did the bug hunting proposed a simple fix that we'll include below. We recommend not skipping the full agent bug report that is attached above, since it also points out another tangential issue, and a thorough breakdown of the problem.

Proposed Fix

In dist/extensions/discord/channel-CGp7scNs.js, change line 346:

  function parseDiscordExplicitTarget(raw) {
      try {
          const target = parseDiscordTarget(raw, { defaultKind: "channel" });
          if (!target) return null;
          return {
-             to: target.id,
+             to: target.normalized,
              chatType: target.kind === "user" ? "direct" : "channel"
          };
      } catch {
          return null;
      }
  }

target.normalized preserves the full user:<id> or channel:<id> string, preventing downstream code from reclassifying the target.

extent analysis

TL;DR

Apply the proposed fix to dist/extensions/discord/channel-CGp7scNs.js to prevent the to field from being clobbered.

Guidance

  • Review the proposed fix and understand how it addresses the issue by preserving the full user:<id> or channel:<id> string.
  • Verify that the target.normalized property is correctly set and used downstream to prevent reclassification of the target.
  • Test the fix by triggering a heartbeat message and checking the delivery queue for successful delivery.
  • If issues persist, review the full agent bug report for additional insights and potential tangential issues.

Example

The proposed fix is already provided in the issue body, which changes the parseDiscordExplicitTarget function to use target.normalized instead of target.id.

Notes

The fix assumes that the target.normalized property is correctly set and used by downstream code. If this is not the case, additional changes may be necessary.

Recommendation

Apply the proposed workaround by changing the parseDiscordExplicitTarget function to use target.normalized instead of target.id, as this directly addresses the root cause of the issue.

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…

FAQ

Expected behavior

Heartbeat message should be delivered to Discord DMs. Note that our configuration explicitly has all heartbeat messages enabled for discord.

#GPU setup#container setup#orchestration issue#cache issue#memory leak

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 [Bug]: Discord DM heartbeats erroneously resolve `user:<snowflake>` to `channel:<snowflake>` [1 comments, 2 participants]