Utilities

Cron Expression Generator & Parser

Build cron expressions visually or paste existing ones to decode them. See the next execution times and get human-readable descriptions.

Quick Presets

Generated Expression

* * * * *

Every minute

Next 5 Executions

1Wed, Apr 29, 2026, 11:29
2Wed, Apr 29, 2026, 11:30
3Wed, Apr 29, 2026, 11:31
4Wed, Apr 29, 2026, 11:32
5Wed, Apr 29, 2026, 11:33

Cron Syntax Reference

SymbolMeaningExample
*Any value* (every minute)
*/nEvery n units*/15 (every 15 min)
nSpecific value30 (at minute 30)
a,bMultiple values1,15 (1st and 15th)
a-bRange1-5 (Mon to Fri)

Automate your incident response

Reduce MTTR by 90% with AI-powered root cause analysis. Free to start.

Try Uptimes.ai Free

Cron Expressions Explained

Cron is a time-based job scheduling system originally built for Unix operating systems. The name comes from the Greek word "chronos" (time). A cron expression defines when a job should run using five fields that specify the minute, hour, day of month, month, and day of week.

In modern DevOps, cron expressions are used far beyond simple Unix cron jobs. They schedule Kubernetes CronJobs, GitHub Actions workflows, monitoring checks, database backups, log rotation, and alert evaluations. Understanding cron syntax is an essential skill for any SRE or DevOps engineer.

Common Cron Patterns for SRE

SRE teams commonly use cron expressions for: health checks (every 1-5 minutes), metric aggregation (every 15 minutes), log cleanup (daily at low-traffic hours), certificate rotation checks (weekly), capacity reports (monthly), and SLA reports (quarterly). The key is choosing frequencies that balance freshness with system load.

Automate Monitoring with Uptimes.ai

Instead of manually scheduling monitoring checks with cron, Uptimes.ai provides continuous automated monitoring with AI-powered alerting. Our platform polls your Datadog and Prometheus metrics, correlates alerts across services, and automatically investigates incidents when they occur.

Frequently Asked Questions

What is a cron expression?+
A cron expression is a string of five fields separated by spaces that defines a schedule. The fields represent: minute (0-59), hour (0-23), day of month (1-31), month (1-12), and day of week (0-6, where 0 is Sunday). Cron expressions are used by cron daemons on Unix systems, Kubernetes CronJobs, CI/CD pipelines, and monitoring tools to schedule recurring tasks.
What does */5 * * * * mean?+
The expression */5 * * * * means "every 5 minutes." The */5 in the minute field means "every 5th minute" (0, 5, 10, 15, ..., 55). The asterisks in the remaining fields mean "every hour, every day of the month, every month, every day of the week."
How do I schedule a cron job for weekdays only?+
Use the day-of-week field (the 5th field). For weekdays (Monday through Friday), use 1-5. Example: "0 9 * * 1-5" runs at 9:00 AM every Monday through Friday. You can also use comma-separated values: "0 9 * * 1,2,3,4,5".
What is the difference between 5-field and 6-field cron?+
Standard Unix cron uses 5 fields (minute, hour, day of month, month, day of week). Some systems like Kubernetes and Spring add a 6th field for seconds at the beginning. This tool generates standard 5-field expressions, which are compatible with most systems including Kubernetes CronJobs.
How do I use cron expressions in Kubernetes?+
Kubernetes CronJobs use standard 5-field cron expressions in the spec.schedule field. Example: apiVersion: batch/v1, kind: CronJob, metadata.name: my-job, spec.schedule: "0 */6 * * *" runs every 6 hours. Kubernetes also supports @yearly, @monthly, @weekly, @daily, and @hourly shortcuts.