Summary

Cron job announce delivery ignores the channel field in the job's delivery config and routes to the wrong channel. The delivery config explicitly specifies channel: "telegram" but the system attempts delivery via whatsapp (which is not configured), producing Unsupported channel: whatsapp.

Environment

• OpenClaw: 2026.2.6-3
• OS: macOS 25.2.0 (arm64)
• Node: v24.7.0
• Gateway: local, port 18789
• Channels configured: telegram, slack (no whatsapp)

Delivery Config on Job

{
  "mode": "announce",
  "channel": "telegram",
  "to": "8519725519"
}

Error History

The job has been erroring for weeks with two different failure modes:

1. ~40 runs: Error: An API error occurred: channel_not_found (Slack API error, suggesting it tried Slack despite config saying telegram)
2. Last 2 runs: Unsupported channel: whatsapp (whatsapp is not configured at all)

The job payload itself always succeeds (git backup completes fine) — only the announce delivery fails.

Other Jobs Work Fine

12+ other cron jobs with identical delivery config (channel: "telegram", to: "8519725519") deliver successfully. Only this one job (hourly backup, sessionTarget: "isolated", payload.kind: "agentTurn") routes incorrectly.

Workaround

Switching delivery to channel: "slack" resolved the issue.

Possibly Related

• Bug: Subagent announce delivery fails with wrong WhatsApp account (multi-account routing) #1058 — Subagent announce delivery uses wrong account (accountId not propagated)
• [Bug]: Session replies not routing to Telegram when webchat is also active #5531 — Session replies not routing to Telegram when webchat active
• Telegram unable to receive cron message #5339 — Telegram unable to receive cron messages