Pick the instant you are reasoning about
“Next run” depends on when you ask. Set a reference date and time to answer questions like “when did this last run before the outage at 03:12?” (switch to Previous) or “what runs during the release freeze?”. The reference is interpreted in the selected time zone, and each row shows the local time, the UTC instant and the offset in force.
Add up to three extra display zones to see the same instants for teammates in other regions. Rows affected by daylight saving are labelled — skipped wall times, catch-up runs, or the first and second pass of a repeated hour — and you can export the list as CSV, JSON or an .ics file for your calendar.
Try these
Questions
Why might my server run at a different time than shown?
Cron runs in the daemon’s time zone (or CRON_TZ on cronie, spec.timeZone on Kubernetes). Make sure the zone here matches the host, and remember GitHub Actions and AWS EventBridge rules always use UTC.
How far ahead can it look?
Up to 400 years for sparse schedules such as 29 February, bounded by each dialect’s year range (Quartz 2099, AWS 2199).