Using OpenClaw Cron Jobs for Scheduled Tasks Instead of Heartbeat Monitoring

OpenClaw Cron Jobs for Scheduled Work

A Reddit user highlights a common pattern where people misuse HEARTBEAT.md for scheduled tasks like checking email, summarizing calendars, or scanning Reddit, which they describe as expensive and unreliable. The post recommends using cron jobs instead for scheduled tasks that run at specific times with specific prompts.

Key Commands and Configuration

The source provides two concrete cron job examples:

openclaw cron add \
 --name "Morning Briefing" \
 --cron "15 7 * * *" \
 --tz "Asia/Kolkata" \
 --session isolated \
 --message "Compile a morning briefing. Check in this order: 1. Calendar: meetings today, flag anything before 10am or overlapping. 2. Email: unread inbox. URGENT = from [name1], [name2], [name3] or containing deadline/asap/urgent. Everything else = sender + subject only. 3. Weather: high, low, rain. One line. 4. Priorities: check [sheet url] for anything due today or overdue. One telegram message. Urgent stuff first. Under 15 lines. No filler. If genuinely nothing noteworthy: quiet morning, nothing urgent. Do not invent things to report."

openclaw cron add \
 --name "Email Triage" \
 --cron "0 9,11,13,15,17 * * *" \
 --tz "Asia/Kolkata" \
 --session isolated \
 --message "Scan inbox for new unread emails. Group into: REPLY TODAY: needs my response before end of day. THIS WEEK: important but not urgent. FYI: newsletters, notifications. Only message me on telegram if REPLY TODAY has items. Do not draft replies. Do not suggest responses. Just sort and report."

Critical Session Isolation

The post emphasizes the importance of the --session isolated flag, which ensures each cron run gets a fresh context. Without this flag, cron job context (like calendar or email information) can bleed into other conversations, causing the agent to reference unrelated information during normal interactions. The user gives an example: "before we start, don't forget your 2pm with nisha" appearing during debugging.

Known Bugs and Testing

The source notes that isolated sessions have had bugs across versions, specifically mentioning issues #10804, #13546, and #44257 where jobs silently don't execute. The recommendation is to test crons after every update using openclaw cron runs --id <jobId> to verify they actually fired.