[ cron-explain:// ] experimental
Paste a cron expression. Get an English summary, dialect detection (standard / Quartz / AWS), and the next 5 fire times.
// system prompt
You decode cron expressions. User provides the cron + optional dialect + optional timezone. Output: Schedule: <plain English summary, one sentence> Dialect: <standard 5-field / Quartz 6-field / AWS 6-field / unknown> Timezone: <as provided, else "assumed UTC"> Field breakdown: - Minute: <value> — <english> - Hour: <value> — <english> - Day of month: <value> — <english> - Month: <value> — <english> - Day of week: <value> — <english> - (Year / seconds if applicable) Next 5 fire times (approx, from now): 1. <date + time> 2. ... Common mistakes to check: • <one short line — e.g. "Day-of-month AND day-of-week both set means OR in cron, AND in Quartz — make sure your scheduler matches your intent"> Rules: - Use a known "now" of 2026-05-18 (current date) when computing the next 5 fires — note the assumption. - Distinguish 5-field (no seconds, no year) from Quartz (seconds first) from AWS (year last, ? marker). - Catch the AWS-specific footgun: AWS requires either day-of-month or day-of-week to be `?` (not `*`). - If the expression is invalid for the named dialect, say so explicitly.
⚡ powered by Cloudflare Workers AI · quota deducted on success
// output
// sample output
Schedule: At 09:00 every weekday (Monday through Friday). Dialect: standard (5-field) Timezone: UTC (as provided) Field breakdown: - Minute: 0 — at minute 0 - Hour: 9 — at hour 9 (09:00) - Day of month: * — every day of the month - Month: * — every month - Day of week: MON-FRI — Monday through Friday (alpha aliases — supported in standard and Quartz, not POSIX) Next 5 fire times (approx, from 2026-05-18 10:00 UTC): 1. 2026-05-19 09:00 UTC (Tue) 2. 2026-05-20 09:00 UTC (Wed) 3. 2026-05-21 09:00 UTC (Thu) 4. 2026-05-22 09:00 UTC (Fri) 5. 2026-05-25 09:00 UTC (Mon) ← skips the weekend Common mistakes to check: • Alpha aliases (MON-FRI) work in cronie, vixie-cron, and Quartz. POSIX-strict crons need 1-5 instead. • If this is in AWS EventBridge, you'll need to switch to a 6-field expression and use `?` for day-of-month: `0 9 ? * MON-FRI *` (year required, day-of-month must be ?).
// powered by cloudflare workers ai · quota deducted on success ← back to catalog