WhatsApp cron announce 兜底：隔离任务成功但未送达时的回退策略
问题/场景：isolated cron 在 WhatsApp announce 下可能出现 `No reply from agent`，run 成功但消息不达。前置条件：已接入 WhatsApp（Baileys）并可复现实例。实施步骤：先用最小任务复现→检查 run 与日志分歧→将关键通知改为可追踪兜底路径（如明确 recipient + 失败告警）→升级后回归。关键命令：cron add/run/runs。验证：触发后 WhatsApp 实收且日志无 No reply。风险：仅看 run summary 容易误判已送达。
GITHUBDiscovered 2026-02-15Author gchlebus
Prerequisites
- WhatsApp channel is configured and can receive regular test messages.
- You can run cron commands and inspect gateway logs.
Steps
- Create a minimal isolated cron job with announce delivery to a known WhatsApp recipient.
- Trigger with `openclaw cron run <jobId>` and compare `cron runs` output with actual WhatsApp delivery.
- When mismatch appears, record `No reply from agent` evidence and enable explicit fallback notification path.
- After upgrading/patching, rerun the same test case to confirm announce path recovery.
Commands
openclaw cron add --session isolated --announce --channel whatsapp --to '<target>' --message 'Say hello'openclaw cron run <jobId>openclaw cron runs --id <jobId>Verify
Run status is ok, gateway logs contain no `No reply from agent`, and WhatsApp receives the message.
Caveats
- CLI flags may evolve; confirm against current `openclaw cron --help` before automation rollout（需验证）.
- Do not remove manual monitoring until multiple successful runs are observed.
Source attribution
This tip is aggregated from community/public sources and preserved with attribution.
Open original source ↗