Skip to content
OperatorNest

Cron expression generator

Write a cron schedule and inspect its next runs in a selected time zone.

Example weekday schedule: At 09:00 on weekdays, shown in the selected time zone.

Schedule

Build from choices or paste an expression. Numeric fields, stars, lists, ranges, and steps can be previewed.

Build a schedule

Minute hour day-of-month month day-of-week

GitHub uses five fields. Its schedule defaults to UTC and supports an IANA time zone in workflow configuration.

GitHub schedule docs, checked 28 September 2026

Weekday example ready.

Schedule in words

At 09:00 every Monday through Friday. The selected time zone is separate from the expression.

Next ten matching times

Calculated from the current minute in the selected time zone. These are matching times, not a promise that the scheduler will run.

  1. Calculating schedule…

GitHub scheduled jobs can be delayed or dropped during high load.

Dialect notes

Embed this tool

Copy this snippet to show the tool on your site.

How it works

The preview checks future minutes against the selected dialect in the selected IANA time zone, including Quartz seconds and AWS years.

Special calendar characters are flagged. Matching times are not receipts that a service ran the job.

Sources and checked dates

Limits

  • Next-run previews cover numeric fields, stars, lists, ranges, steps, Quartz seconds, and AWS years within 366 days. L, W, #, and named fields need the target scheduler.
  • Actual execution may be delayed or skipped by the scheduler. Confirm time zone and daylight-saving behavior in that service.

Common questions

Which cron syntax does the preview support?
Numeric fields with stars, lists, ranges, and steps. It also handles Quartz seconds and AWS year fields. Special calendar characters and names need the target scheduler.
What happens at a daylight-saving change?
The preview converts candidate instants through the selected IANA time zone. A wall-clock time that does not exist cannot match; repeated local times can match twice.
Will GitHub run exactly at the listed time?
No. GitHub says scheduled workflows can be delayed during high load and some jobs may be dropped. The list describes matching times, not execution receipts.

OperatorNest can take on repeat work, check with you before consequential steps, and leave a receipt for the result. See how an always-on operator works.

Hand off your first task tonight.

Tell us your email and what you'd hand off first. We'll send your access details and help you set up your operator.