What should I do if OpenClaw (Lobster) Scheduled Tasks Don't Execute?

OpenClaw (lobster) timed tasks are not executed, first check the scheduler, job list, recent run history, and gateway logs. Don't just look at whether the task is written into the file, because cron is not enabled, the gateway is not running, the job time is not up, and the main lane is busy, which may cause it to look "not triggered".

Troubleshooting commands

1. openclaw status
2. openclaw gateway status
3. openclaw cron status
4. openclaw cron list
5. openclaw cron runs --id <jobId> --limit 20
6. openclaw logs --follow

Common log meanings

• cron: scheduler disabled: The scheduler is turned off and the task does not run automatically.
• requests-in-flight: The main mission channel is busy, and the wake-up is delayed.
• unknown accountId: The target account does not exist.
• No runs record: first check whether the job is actually registered and whether the time expression is correct.

Scheduled tasks are best suited for low-risk, repeatable, and checkable work, such as morning reports, data collation, and reminders. For tasks involving emailing, payment, and deleting files, it is recommended to use Lobster approval or manual confirmation, and not be completely unattended.

Official open source address: https://github.com/openclaw/openclaw.

Also, make sure that the channel where the mission was delivered is still alive. Just because Gateway can run doesn't mean Telegram, Slack, or WebChat can deliver, and when the channel token expires, the task may have been executed, but the result didn't go where you saw it.