CloudPlans Docs

Time zones and schedules

Every Plan runs in the time zone you choose for that Plan, not in your browser's or the server's time zone. The schedule (start time, duration and active days) and any exceptions are always interpreted in the Plan's time zone.

Daylight saving time (DST)

Zones that observe daylight saving time (for example Madrid / Paris, London / Lisbon, New York, Los Angeles, Sydney, Auckland) are stored as real regional time zones. A Plan set to start at 08:00 in Madrid therefore starts at 08:00 local time all year, across the spring and autumn clock changes.

Plans created before this was introduced may still use a fixed UTC offset (for example UTC+01:00). A fixed offset does not follow clock changes, so such a Plan starts one hour early or late for part of the year. Open the Plan, pick the regional zone from the list and save it to fix this.

Zones without daylight saving (for example Dubai, Mumbai, Tokyo / Seoul) remain fixed offsets, which is correct for them.

When is a Plan evaluated?

Plans are evaluated once per hour. A start, stop or pause takes effect on the first evaluation at or after the time you set, not necessarily at that exact minute.

Exceptions (pauses)

An exception pauses a Plan between two dates and times. Both are entered in the Plan's time zone, shown in the form so there is no ambiguity.