#Clawdbot tried to set up a cron job and it crashed the server

1 messages · Page 1 of 1 (latest)

alpine grotto
#

I asked it to do a scheduled task for the first time and I think it crashed becasue of it. this is the session output:
I’m going to check the local OpenClaw docs for the right way to set up scheduled check-ins, since this is exactly the kind of thing that should be done with a proper schedule instead of me hand-waving it.
Warning: workdir "/workspace" is unavailable; using "/home/openclaw/.openclaw/workspace".

/usr/lib/node_modules/openclaw/docs/zh-CN/reference/session-management-compaction.md:84:- 定时任务：cron:<job.id>
/usr/lib/node_modules/openclaw/docs/zh-CN/tools/index.md:5:summary: OpenClaw 的智能体工具接口（browser、canvas、nodes、message、cron），替代旧版 openclaw-* Skills
/usr/lib/node_modules/openclaw/docs/zh-CN/tools/index.md:18:OpenClaw 为 browser、canvas、nodes 和 cron 暴露一流的智能体工具。
/usr/lib/node_modules/openclaw/docs/zh-CN/tools/index.md:158:- group:automation：cron、gateway
/usr/lib/node_modules/openclaw/docs/zh-CN/tools/index.md:402:### cron

regal saffronBOT
#

That snippet doesn’t look like a crash from cron itself — it’s just the agent running a quick grep over the local docs to find the cron section.

Two key bits in what you pasted:

  • Warning: workdir "/workspace" is unavailable; using "/home/openclaw/.openclaw/workspace".
    This is not fatal. It just means whatever environment you’re running in (often Docker / a sandbox) doesn’t have /workspace mounted, so OpenClaw falls back to the default workspace path.

  • The /usr/lib/node_modules/openclaw/docs/... lines are just “files where the word cron appears”.

If the Gateway actually “crashed”, the useful evidence will be in the gateway logs around that moment. Can you paste these outputs?

openclaw --version
openclaw gateway status
openclaw status --all