Platform Guides
Cron Expressions by Platform
Every platform has quirks. Pick yours for syntax rules, common patterns, config examples, and gotchas.
CI/CD5-field
GitHub Actions
GitHub Actions supports scheduled workflows using standard 5-field cron syntax.
*/5 * * * *every 5 minutesView guide→
DevOps5-field
Kubernetes
Kubernetes CronJob uses standard 5-field cron syntax to schedule batch jobs.
*/5 * * * *every 5 minutesView guide→
AWS6-field
AWS EventBridge
AWS EventBridge (formerly CloudWatch Events) uses a 6-field cron syntax that adds a 'year' field.
0/5 * * * ? *every 5 minutesView guide→
GCP5-field
GCP Cloud Scheduler
Google Cloud Scheduler uses standard Unix cron syntax (5 fields) but adds full timezone support.
*/5 * * * *every 5 minutesView guide→
Azure6-field
Azure Functions
Azure Functions Timer Trigger uses a 6-field NCRONTAB expression where the first field is seconds (not minutes).
0 */5 * * * *every 5 minutesView guide→
Platform Comparison
| Platform | Fields | Timezone |
|---|---|---|
| crontab | 5 | System TZ |
| GitHub Actions | 5 | UTC only |
| Kubernetes | 5 | Cluster TZ (1.27+) |
| AWS EventBridge | 6 | UTC only |
| GCP Cloud Scheduler | 5 | Any IANA TZ |
| Azure Functions | 6 | UTC (configurable) |
Test any cron expression — any platform
Paste your cron expression to get a plain-English translation, next run times, and lint warnings for common mistakes.