openclaw - 💡(How to fix) Fix [Bug]: Telegram message tool fails with stale dist chunk import (ERR_MODULE_NOT_FOUND action-runtime/probe hash mismatch) [1 comments, 2 participants]

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

Telegram outbound via the message tool fails with ERR_MODULE_NOT_FOUND because the running gateway is trying to import stale hashed dist/ chunks that do not exist on disk.

In this case the failing import is:

• missing: dist/action-runtime-JVgOnJIQ.js
• imported from: dist/probe-gofM6JmN.js

But the installed package on disk contains different sibling chunks instead:

• present: dist/action-runtime-CYqPrZR6.js
• present: dist/probe-DoAxOwuy.js

This looks like the same stale-hash / mixed-runtime family as prior ERR_MODULE_NOT_FOUND upgrade issues, but here the symptom is specifically that Telegram message.action=send is unusable even though the Telegram channel shows ON / OK in openclaw status.

Steps to reproduce

1. Use OpenClaw on Linux with Telegram enabled.
2. Call the message tool with action=send to a Telegram DM target.
3. Observe the tool fail immediately with:

Cannot find module '/usr/lib/node_modules/openclaw/dist/action-runtime-JVgOnJIQ.js' imported from /usr/lib/node_modules/openclaw/dist/probe-gofM6JmN.js

Expected behavior

message.action=send should deliver the Telegram message, or at worst fail with a Telegram/API error — not a local module-resolution error for missing hashed runtime chunks.

Actual behavior

The tool fails locally before any Telegram API call is made:

Cannot find module '/usr/lib/node_modules/openclaw/dist/action-runtime-JVgOnJIQ.js' imported from /usr/lib/node_modules/openclaw/dist/probe-gofM6JmN.js

Additional oddity: the installed CLI version and the running gateway version do not match.

• openclaw --version → 2026.5.3 (06d46f7)
• openclaw status → Gateway self ... app 2026.5.2

A controlled restart and a manual restart were both attempted. After restart, the gateway still reported 2026.5.2 and the message tool still failed with the exact same missing-module error.

OpenClaw version

CLI installed: 2026.5.3 (06d46f7) Running gateway self reported by openclaw status: 2026.5.2

Operating system

Linux 6.8.12-18-pve (x64)

Install method

Global install under /usr/lib/node_modules/openclaw

Model

openai-codex/gpt-5.4

Provider / routing chain

Telegram channel configured; failure happens before outbound provider call

Additional provider/model setup details

Telegram appears healthy in openclaw status:

• Channel: Telegram ON
• State: OK
• accounts 1/1

Logs, screenshots, and evidence

openclaw --version
OpenClaw 2026.5.3 (06d46f7)

openclaw status
Gateway ... app 2026.5.2
Gateway self ... app 2026.5.2
Telegram ON / OK

message tool result:
{
  "status": "error",
  "tool": "message",
  "error": "Cannot find module '/usr/lib/node_modules/openclaw/dist/action-runtime-JVgOnJIQ.js' imported from /usr/lib/node_modules/openclaw/dist/probe-gofM6JmN.js'"
}

File existence on disk:
- MISSING dist/action-runtime-JVgOnJIQ.js
- MISSING dist/probe-gofM6JmN.js
- EXISTS  dist/action-runtime-CYqPrZR6.js
- EXISTS  dist/probe-DoAxOwuy.js

Impact and severity

Affected: outbound messaging through the message tool (at least Telegram)

Severity: High. The agent can still converse in-session, but explicit tool-driven delivery is broken. This blocks cases where OpenClaw expects message.action=send for proactive delivery or media send flows.

Frequency: 100% so far on this installation.

Additional information

This smells more like a stale / mixed dist runtime than a Telegram-specific bug, because the failure is a local ERR_MODULE_NOT_FOUND for hashed runtime chunks rather than a provider/API error.