Corn jobs | Friends of the Crustacean 🦞🤝 | Page 1

cerulean verge May 10, 2026, 11:01 AM

#

Can openclaw not set up permanent crown jobs my agent says "auto expires in 7 days" is that normal how do I stop it I'm trying to set a morning news brief everyday

rare pantherBOT May 10, 2026, 11:01 AM

#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

clear kindleBOT May 10, 2026, 11:01 AM

#

Yep — OpenClaw can do permanent recurring cron jobs. The “auto expires in 7 days” bit is usually the background task/run record, not the cron schedule itself. Completed task records are retained for 7 days and then pruned; the actual recurring cron job should persist until you disable/delete it.

Check the real scheduler state with:

openclaw cron list
openclaw cron show <job-id>

For a daily morning news brief, you want a recurring --cron, not a one-shot --at, e.g.:

openclaw cron add \
  --name "Morning news brief" \
  --cron "0 7 * * *" \
  --tz "America/New_York" \
  --session isolated \
  --message "Prepare a concise morning news brief with the top stories I care about." \

#

  --announce \
  --channel discord \
  --to "channel:YOUR_CHANNEL_OR_THREAD_ID"

If openclaw cron list doesn’t show it, then the agent probably created a temporary task/reminder instead of a scheduler job. Also paste openclaw --version if it still looks weird — version mismatches are a common cause of cron confusion.

Docs: https://docs.openclaw.ai/automation/cron-jobs and https://docs.openclaw.ai/cli/cron

cerulean verge May 10, 2026, 11:03 AM

#

The agent said this exactly

"✅ Cron set up. Job ID: 5c6a9ee5

Schedule: Daily at 02:03 UTC = 7:33 AM IST (3 min nudge off the zero, like I mentioned)

What it'll do every morning:

Pull Delhi weather via the weather skill
Pull tech/AI news via the news-summary skill (already filtered for tech only)
Compose a VERIDIAN-styled brief: 🌤️ Delhi weather → 📰 AI/Big Tech/Hardware/Dev sections → witty signoff
Drop it straight into your Telegram

⚠️ Two things you should know, Boss:

Auto-expires after 7 days — that's a hardcoded limit on the OpenClaw cron tool. After 7 days from now (so ~May 17), the job dies and I'll need to re-arm it. I can set myself a reminder to do that, or you can just ping me once a week.
Marked "session-only" even though I asked for durable storage — the harness didn't honor the persistence flag for this job type. Realistically the Telegram bridge stays running so it should be fine, but if my session ever fully resets, the cron's gone.

If you want bulletproof durability (no 7-day cap, survives any restart), I can move it to a remote scheduled agent instead — but that runs in Anthropic's cloud, not through this Telegram session, and costs more. Your call.

First brief lands tomorrow morning. 🤵‍♀️"

clear kindleBOT May 10, 2026, 11:03 AM

#

That reply is almost certainly wrong. I checked the current docs/source shape: OpenClaw cron jobs are durable Gateway scheduler jobs, stored under ~/.openclaw/cron/jobs.json, and recurring --cron jobs do not have a hardcoded 7-day expiry.

The 7-day thing is for background task records: completed task/run history is kept for 7 days, then pruned. That does not mean the cron schedule dies.

What to run:

openclaw --version
openclaw cron show 5c6a9ee5
openclaw cron list

If cron show 5c6a9ee5 shows a recurring cron expression like 3 2 * * * and no delete-after-run / one-shot at schedule, you’re fine. If it only appears in openclaw tasks list, then the agent created/inspected a task record, not a real cron job.

Also: “session-only” sounds like session/thread binding language, not cron durability. For bulletproof daily brief, use an isolated recurring cron job with announce delivery to Telegram:

openclaw cron add \

#Corn jobs