Cron Job Delivery System Completely Broken
Problem: OpenClaw cron jobs execute successfully but never deliver messages to Telegram, regardless of delivery method.
Environment:
• OpenClaw: 2026.2.1 (latest)
• Gateway: Running and responding
• Cron jobs: Multiple types tested
Methods Tested:
1. Isolated Sessions (agentTurn)- Session target: isolated
- Payload kind: agentTurn
- Wake mode: next-heartbeat
- Result:
Delivers "HEARTBEAT_OK" instead of message content
2. Main Sessions (systemEvent)- Session target: main
- Payload kind: systemEvent
- Wake mode: next-heartbeat
- Result: Job runs successfully but no delivery occurs
Evidence from Logs:
Test job executed successfully:
{"action":"finished","status":"ok","summary":"
TEST: Main session cron delivery","runAtMs":1770104858001,"durationMs":4}
User reports: "Didn't receive a thing..."
Expected: Message delivered to Telegram
Actual: Job shows "ok" status but user receives nothing
Questions:
1. Is this related to Issue #3589 (heartbeat prompt bug)?
2. Are main session systemEvents supposed to deliver automatically?
3. What's the correct delivery mechanism for cron jobs?
4. Any known fixes or workarounds?
Context: This affects all cron delivery methods - both isolated and main sessions fail to deliver actual message content.
Environment:
• OpenClaw: 2026.2.1 (latest)
• Gateway: Running and responding
• Cron jobs: Multiple types tested
Methods Tested:
1. Isolated Sessions (agentTurn)- Session target: isolated
- Payload kind: agentTurn
- Wake mode: next-heartbeat
- Result:
Delivers "HEARTBEAT_OK" instead of message content2. Main Sessions (systemEvent)- Session target: main
- Payload kind: systemEvent
- Wake mode: next-heartbeat
- Result:
Job runs successfully but no delivery occursEvidence from Logs:
Test job executed successfully:{"action":"finished","status":"ok","summary":"
TEST: Main session cron delivery","runAtMs":1770104858001,"durationMs":4} User reports: "Didn't receive a thing..."Expected: Message delivered to Telegram
Actual: Job shows "ok" status but user receives nothing
Questions:
1. Is this related to Issue #3589 (heartbeat prompt bug)?
2. Are main session systemEvents supposed to deliver automatically?
3. What's the correct delivery mechanism for cron jobs?
4. Any known fixes or workarounds?
Context: This affects all cron delivery methods - both isolated and main sessions fail to deliver actual message content.
The AI that actually does things. Emails, calendar, home automation - all from your favorite chat app. New shell, ready to help. The lobster way.
83,815Members
Resources
Similar Threads
Was this page helpful?
