🐛 Bug Report: Cron Jobs Not Firing
Environment:
• OpenClaw v2026.2.3-1
• Windows 11, Node v24.13.0
• Model: claude-opus-4-5
Issue:
Cron jobs scheduled but never execute. Jobs silently skip their time, nextRunAtMs advances without firing.
Repro:
1. Create job with sessionTarget: "isolated", payload.kind: "agentTurn"
2. Schedule time passes
3. Job never fires — no session spawned, no delivery
Evidence:
• cron list shows correct schedule
• cron status shows enabled: true
• cron runs --jobId <id> returns empty entries
• Gateway confirmed running at scheduled times
• Restart (SIGUSR1) didn't fix
Jobs affected: All isolated agentTurn jobs (Morning Briefing 7AM, Twitter Digest 7:30AM, X Post Draft 9AM)
Workaround: Manual execution from main session works.
Question: Known issue with isolated agentTurn cron on Windows? Missing config?
• OpenClaw v2026.2.3-1
• Windows 11, Node v24.13.0
• Model: claude-opus-4-5
Issue:
Cron jobs scheduled but never execute. Jobs silently skip their time, nextRunAtMs advances without firing.
Repro:
1. Create job with sessionTarget: "isolated", payload.kind: "agentTurn"
2. Schedule time passes
3. Job never fires — no session spawned, no delivery
Evidence:
• cron list shows correct schedule
• cron status shows enabled: true
• cron runs --jobId <id> returns empty entries
• Gateway confirmed running at scheduled times
• Restart (SIGUSR1) didn't fix
Jobs affected: All isolated agentTurn jobs (Morning Briefing 7AM, Twitter Digest 7:30AM, X Post Draft 9AM)
Workaround: Manual execution from main session works.
Question: Known issue with isolated agentTurn cron on Windows? Missing config?
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
Recent Announcements
Similar Threads
Was this page helpful?
