Description

Cron jobs with delivery: { mode: "announce", channel: "telegram", to: "USER_ID" } show "delivered: true" in cron run history but no message is ever sent to Telegram.

Steps to Reproduce

1. Create a cron job with Telegram announce delivery:

openclaw cron add --name test --cron "0 17 * * *" --tz America/Chicago --message "Hello" --channel telegram --to 8539774246

2. Wait for cron to run or trigger manually with openclaw cron run <id>

3. Check cron runs: openclaw cron runs --id <id>

Expected: Message appears in Telegram
Actual: Cron shows "delivered: true" but no Telegram API call is made

Investigation

• Manual openclaw message send --channel telegram --target X --message Y works fine
• Cron shows "deliveryStatus: "delivered"" but there is NO network activity in logs for Telegram
• The cron appears to mark as delivered without actually calling the Telegram API

Environment

• OpenClaw 2026.3.7
• macOS
• Telegram channel configured with bot token

Logs

No Telegram network activity appears when cron runs - the announce delivery path appears broken.

Workaround

Using --system-event with sessionTarget: main works for webchat. For Telegram, using openclaw message send manually works.