Read five-field cron schedules across timezones

How to use the workspace

1. Enter exactly five fields: minute, hour, day of month, month and day of week.
2. Set an IANA timezone and optionally a reference ISO instant with an offset.
3. Preview ten runs and compare their local displays, ISO instants and UTC offsets.

A concrete starting point

*/15 9-17 * * MON-FRI
Every fifteen minutes during hours 9 through 17 on weekdays
Timezone: America/New_York

An hour range includes the whole final hour. This expression can include 17:45, not just 17:00.

Read the result carefully

Day-of-month and day-of-week constraints use OR matching. The pinned cron-parser library determines DST behavior; review runs around clock changes if timing matters. The output is a preview, not a background scheduler.

Common mistakes to avoid

• Six-field expressions with seconds are not accepted.
• Extensions such as L, W, #, ? and @ aliases are outside this release.
• A cloud service may use a different parser or timezone default. Compare against that service before deploying a schedule.

Limits & privacy

Standard lists, ranges, steps and month/day names only. Exactly ten upcoming runs are requested by the UI. No job is created or executed.