Isolated cron job with `every` schedule never runs
Setup:
- OpenClaw version: 2026.2.3-1
- Created job via tool call with:
{
"schedule": {"kind": "every", "everyMs": 180000},
"sessionTarget": "isolated",
"payload": {"kind": "agentTurn", "message": "...", "model": "sonnet"},
"delivery": {"mode": "announce", "channel": "signal", "to": "+1234567890"}
}
Observed behavior:
- Job appears in
-
-
- After 2+ hours, still no runs despite 3-minute interval
Expected behavior:
- Job should run every 3 minutes and deliver announce to Signal
Questions:
1. Does adding a new
2. Is there something wrong with my job config?
3. How can I debug why the scheduler considers it "not-due"?
- OpenClaw version: 2026.2.3-1
- Created job via tool call with:
{
"schedule": {"kind": "every", "everyMs": 180000},
"sessionTarget": "isolated",
"payload": {"kind": "agentTurn", "message": "...", "model": "sonnet"},
"delivery": {"mode": "announce", "channel": "signal", "to": "+1234567890"}
}
Observed behavior:
- Job appears in
cron list-
cron runs --id <jobId>{"entries": []}-
cron run <jobId>{"ran": false, "reason": "not-due"}- After 2+ hours, still no runs despite 3-minute interval
Expected behavior:
- Job should run every 3 minutes and deliver announce to Signal
Questions:
1. Does adding a new
every2. Is there something wrong with my job config?
3. How can I debug why the scheduler considers it "not-due"?
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?
