🦞ClawTips
← Back to library

GitHub Issue：修复网关重启后 HEARTBEAT_OK 意外发到 Telegram 的流程

针对心跳回包应“静默吞掉”却被公开发群的故障，给出可执行排查与回归步骤，避免群聊噪音和误报。

GITHUBDiscovered 2026-02-13Author napetrov
Prerequisites
  • OpenClaw agent has heartbeat enabled and bound to Telegram chat/group.
  • You can restart gateway and inspect first heartbeat behavior after restart.
Steps
  1. Reproduce on current stable build: restart gateway and wait for first heartbeat cycle.
  2. Capture evidence: verify whether literal `HEARTBEAT_OK` appears as visible Telegram message.
  3. Apply fix/patch build and repeat the same restart + first-heartbeat sequence.
  4. Add regression check: run 3-5 restart cycles and assert no visible heartbeat ack reaches chat.
Commands
openclaw gateway restart
openclaw gateway status
openclaw logs --local-time
Verify

After restart, heartbeat is consumed internally and no visible `HEARTBEAT_OK` bot message appears in Telegram.

Caveats
  • Different channel adapters may have different ack-handling paths; Telegram pass does not guarantee all channels（需验证）.
  • If heartbeat task text changed from default prompt, confirm matcher still recognizes ack semantics.
Source attribution

This tip is aggregated from community/public sources and preserved with attribution.

Open original source ↗
Visit original post