Reading a cron expression
A standard cron expression has five fields — minute, hour, day of month, month, and day of week — each accepting a number, a range (1-5), a list (1,15,30), a step (*/15), or a wildcard (*) meaning “every value.” A schedule like 0 9 * * 1-5means “9:00 AM, every weekday” — the builder shows that plain-English translation live as you edit each field.
Why the next-run preview matters
Cron syntax is compact but easy to get subtly wrong — mixing up the day-of-month and day-of-week fields, or misplacing a step value, silently produces a schedule that fires at the wrong time (or far more often than intended). Previewing the next 5 fire times catches that mistake before you deploy the schedule to a real job.
Timezone is the most common cron gotcha
Most schedulers (cron, Kubernetes CronJobs, CI/CD pipelines) evaluate expressions in the server’s configured timezone, not the timezone of whoever wrote the expression. The preview shows fire times in your local browser timezone, but always double-check what timezone your actual scheduler runs in before deploying.
Why use UtilityApps for this
The expression, description, and preview are all computed locally in your browser — no signup, and nothing about your schedule is sent to a server.