2026.2.24 变更应对：Heartbeat 不再向私聊直发后的迁移 Runbook
问题/场景：v2026.2.24 引入 breaking 变更，heartbeat 对 direct/DM 目标默认阻断；旧配置若依赖私聊推送会静默失效。前置条件：你有 cron/heartbeat 流程，且可编辑 gateway 配置。实施步骤：1) 盘点现有 heartbeat 目标；2) 把 DM 目标迁移到群组/频道或改内部执行；3) 对关键提醒改用 cron 精确投递；4) 回归测试 announce/no-delivery 行为；5) 更新运维手册。关键命令：`openclaw gateway status`、`openclaw status --deep`、`openclaw help`。验证方法：heartbeat 仍执行但不再误发私聊，替代通道能按预期收到通知。风险与边界：不同渠道的目标解析规则存在差异，迁移前需逐个验证。来源归因：GitHub release notes。
GITHUBDiscovered 2026-02-26Author openclaw
Prerequisites
- You already run heartbeat or reminder-like background checks.
- Operator can review channel target formats (DM vs group/channel IDs).
Steps
- Review all heartbeat delivery targets and mark which ones are direct-message destinations.
- Move user-facing heartbeat notices to non-DM channels, or disable external delivery.
- For exact reminder times, move critical notices to cron jobs with explicit destination config.
- Run health checks and perform one full heartbeat cycle verification after config changes.
- Update runbook so operators know DM delivery is intentionally blocked by design.
Commands
openclaw gateway statusopenclaw status --deepopenclaw helpVerify
Heartbeat tasks continue to execute, but direct-message destinations no longer receive delivery attempts.
Caveats
- Legacy assumptions about `last` destination can break silently after upgrade.
- Channel adapters may represent direct IDs differently and must be tested one by one（需验证）.
Source attribution
This tip is aggregated from community/public sources and preserved with attribution.
Open original source ↗