← Back to Programming and automationOpenClaw automations
Cron vs heartbeat: when to use each
These two tools solve different timing problems. Cron is for exact scheduled work. Heartbeat is for periodic judgment plus action inside the active session.
Choice ruleIf the clock matters, use cron. If conversational context and periodic judgment matter, use heartbeat.
Decision guide
Which timing tool fits which problem?
CronBest for exact-time reminders, exact schedules, or jobs that should run independently of the main transcript.
HeartbeatBest for periodic checks, batching multiple light checks, or work that benefits from the current conversational context.
Shared ruleNeither tool is a substitute for defining the actual artifact or decision the wake should produce.
Useful examples
Examples of correct scheduling choices
“Remind me at 9:00 AM tomorrow”Use cron because exact time matters more than session context.
“Check inbox, calendar, and open work every 30 minutes”Use heartbeat because batching and current context matter.
“Keep a long-running workline moving until done”Use heartbeat or an active monitoring loop if the main session should keep reacting to progress and stalls.
Open deeper reference links for this page