Cronjob cannot stop retry
✅Solved
I created a simple new cron job
docker compose exec openclaw-gateway /app/openclaw.mjs \
cron add \
--agent main --at 5s --name tmp$(date +%s) \
--message 'run bash: date > /home/node/.openclaw/workspace/tmp.txt'
The job run very successfully, but the cron system think it is failed, and retry like crazy.
docker compose exec openclaw-gateway /app/openclaw.mjs \
cron add \
--agent main --at 5s --name tmp$(date +%s) \
--message 'run bash: date > /home/node/.openclaw/workspace/tmp.txt'
The job run very successfully, but the cron system think it is failed, and retry like crazy.
Solution
That command creates an isolated cron job (because you used
So what’s likely happening is:
- The agent turn runs,
- Then cron tries to announce/deliver the result to the “last route”.
- Inside a fresh Docker/Gateway context there often is no “last route”, so delivery fails → cron marks the run as error and schedules retries/backoff.
Fix options:
--messagepayload.kind=agentTurndelivery.mode=announce--channellastSo what’s likely happening is:
- The agent turn runs,
run bash: date > ...- Then cron tries to announce/deliver the result to the “last route”.
- Inside a fresh Docker/Gateway context there often is no “last route”, so delivery fails → cron marks the run as error and schedules retries/backoff.
Fix options:
Option A (recommended): disable delivery for this job
The AI that actually does things. Emails, calendar, home automation - all from your favorite chat app. New shell, ready to help. The lobster way.
131,281Members
Resources
Recent Announcements
Similar Threads
Was this page helpful?
