GUIDE

Time zones and recurring schedules

Understand why a wall clock reading can describe zero, one or two instants.

On this page

Choose named zones

Use names such as Europe/Copenhagen, America/New_York or Asia/Kathmandu. A region includes historical offset changes. Use UTC for universal time. Fixed offsets such as +05:45 and abbreviations such as EST are not accepted. America/New_York observes seasonal changes.

Example winter → Europe/Copenhagen to America/New_York
15 January 2026, 12:00 → 15 January 2026, 06:00.
Example today instead converts the current time in the source zone.

Handle clock changes

A spring transition can skip a local time. An autumn transition can repeat it. The converter rejects skipped times and lets you choose the earlier or later occurrence of a repeated time.

Europe/Copenhagen · 25 October 2026 · 02:30
First (summer offset +02:00) → 00:30 UTC
Second (winter offset +01:00) → 01:30 UTC
In spring, 29 March 2026 at 02:30 does not exist there. Choose another time.

Read scheduled runs

This preview uses five cron fields and a chosen time zone. It starts strictly after the reference instant. For a daily 02:30 schedule in Copenhagen the spring gap runs at 03:30, and the autumn overlap runs once at the earlier offset. Other schedulers may differ.

Every Friday at 09:00 → 0 9 * * 5
Start after 1 January 2026, 00:00 in Europe/Copenhagen. The first run is 2 January at 09:00.
If Start after itself occurs twice, the choice selects the starting instant only.