Cron vs Heartbeat: Choosing the Right Automation Strategy

When building automated systems in OpenClaw, you’ll often face a decision: should you use cron jobs or the heartbeat system to run your tasks? Both enable automation, but they serve different purposes and excel in different scenarios. Understanding when to use each is key to building efficient, reliable workflows.

The Core Difference

At a high level:

• Heartbeat is for periodic awareness and batched checks within the main agent session.
• Cron is for precise scheduling and isolated, standalone tasks.

Let’s break down when to reach for each.

Use Heartbeat When

The heartbeat system runs your agent on a regular interval (default: every 30 minutes) and gives it a chance to check on things. It’s ideal when:

• You’re doing multiple light checks (email, calendar, weather, messages)
• Context from the main conversation matters
• Exact timing isn’t critical
• You want to minimize API calls and token usage

For example, your agent can use a single heartbeat to:

• Scan for urgent emails
• Check for calendar events in the next 2 hours
• Review project status
• Send a brief check-in if you’ve been quiet

All of this happens in one agent turn, reducing overhead and keeping everything in context.

Use Cron When

Cron jobs are better for tasks that need precision or isolation. Use them when:

• The task must run at an exact time (e.g., 9:00 AM every Monday)
• You need a different model or thinking level (e.g., Opus for weekly analysis)
• The task should run independently of the main session
• It’s a one-shot reminder ("remind me in 20 minutes")
• You want direct delivery to a channel without going through the main agent

Cron jobs can run in isolated sessions, which means they start fresh, don’t pollute your main history, and can use different configurations. They’re perfect for generating daily briefings, running weekly reports, or triggering approvals.

Decision Flowchart

Still unsure? Ask yourself:

1. Need exact timing? → Use cron
2. Need isolation or different model? → Use cron (isolated)
3. Can this be batched with other periodic checks? → Use heartbeat
4. Is it a one-shot reminder? → Use cron with --at

Pro Tips

• Combine both: Use heartbeat for routine monitoring and cron for precision tasks.
• Batch checks: Instead of 5 cron jobs, use one heartbeat to check inbox, calendar, and notifications.
• Cost control: Heartbeat is more efficient for frequent, light checks; use cron with cheaper models for regular isolated tasks.
• Lobster for workflows: For multi-step pipelines with approvals, use Lobster — triggered by either cron or heartbeat.

Final Thoughts

The best automation setups use both mechanisms wisely. Heartbeat keeps your agent aware, while cron ensures precision. Choose based on timing needs, isolation, and context — and don’t be afraid to use both in the same system.

For full details, see the Cron vs Heartbeat documentation.