50+ Cron Expression Examples

This guide collects over 50 practical cron expressions organized by frequency and use case. Each expression is shown with its human-readable description and a common scenario where you would use it. Click the expression link to load it in our Cron Expression Builder and verify the schedule.

Every N Minutes

Minute-level schedules are common for health checks, metrics collection, and real-time data processing.

Hourly Schedules

Hourly jobs handle tasks that need regular attention but not constant monitoring.

Daily Schedules

Daily schedules are among the most common cron patterns, used for backups, reports, and maintenance tasks.

Weekly Schedules

Weekly tasks often run on specific days for reporting, maintenance windows, or recurring meetings.

Monthly Schedules

Monthly schedules handle billing cycles, reports, and periodic audits.

Yearly Schedules

Annual tasks include license renewals, compliance checks, and seasonal operations.

Business Hours Schedules

These expressions target standard business hours and weekdays, common for office automation and SLA monitoring.

Special and Advanced Patterns

These expressions demonstrate advanced features and less common scheduling patterns.

DevOps and CI/CD Patterns

Cron expressions in the context of CI/CD pipelines, infrastructure management, and deployment automation.

Tips for Choosing the Right Schedule

When selecting a cron expression for your use case, consider these practical guidelines:

• Avoid minute 0 of hour 0: Many teams schedule jobs at 0 0 * * * (midnight). This creates resource contention. Consider an offset like 15 0 * * * or 0 1 * * * instead.
• Use business hours for alerts: If a cron job sends notifications to humans, schedule it during waking hours. No one wants a 3 AM Slack message about a non-urgent report.
• Account for job duration: If a job takes 20 minutes to complete, do not schedule it every 15 minutes. Either increase the interval or implement locking to prevent overlapping runs.
• Test with next executions: Always verify your expression by checking the next 5-10 execution times. What looks correct at a glance may surprise you when you see the actual schedule.

Build Your Own Expression

Need a schedule that is not covered here? Use our Cron Expression Builder to visually construct any cron expression, verify it with next execution times, and share it with your team using a URL.