Summary

Scheduled cron jobs are not delivering messages to Telegram. The same messaging functionality works correctly when triggered manually.
This appears to be a regression - similar issues were reported and fixed before (#2937, #5339), but the problem has returned.

Steps to reproduce

1. Configure a scheduled task (cron job) to send messages to Telegram
2. Wait for the scheduled time
3. Observe that messages are not delivered to Telegram

Expected behavior

Messages should be delivered to TeLegram when triggered by scheduLed tasks, just Like when triggered manually

Actual behavior

• Jobs fire at scheduled time (visible in agentsession logs)
• Messages appear in webchat control UI
• BUT messages never reach Telegram

OpenClaw version

2026.2.26

Operating system

macOS 15.6.1

Install method

npm

Logs, screenshots, and evidence

**Cron job config:**

{
    "name":"morning-brief",
    "sessionTarget": "main",
    "wakeMode": "now",
    "payload":{"kind":"systemEvent"，"text":"...",
    state": {
        "lastDeliveryStatus":"not-requested"
    }


Gateway Logs:
2026-02-27T01:16:18.244Z [ws]  res  cron.run 26775ms # cron executed # No sendMessage to telegram follows
2026-02-27T01:52:59.072Z [telegram] sendMessage ok message=116  #  Last manual message, cron at 08:32 never delivered

Impact and severity

No response

Additional information

• Direct message tool calls work perfectly (manual triggers)
• No errors in gateway logs related to this
• This is a known issue that was previously fixed ([Bug]: Cron jobs with wake=now don't deliver to Telegram #2937, Telegram unable to receive cron message #5339) but has regressed

Related Issues

#2937 - Cron jobs with wake=now don't deliverto Telegram (closed: compLeted)e (closed: compLeted)
#5339 - Telegram unable to receive cron messag
#14266 - Isolated cron jobs cannot deliver toTelegram (closed: not_planned)