How do I schedule data pipelines in Sydney time across daylight-saving changes?

Schedule in the named time zone Australia/Sydney (or Australia/Melbourne, Australia/Brisbane and so on), not in UTC and not in a fixed offset such as +10:00. A named zone follows daylight saving automatically: 06:00 stays 06:00 local time whether Sydney is on AEST (UTC+10) or AEDT (UTC+11). A schedule written in UTC moves by an hour in local time every April and October.

What goes wrong with UTC schedules

A job scheduled at 20:00 UTC runs at 06:00 in Sydney during AEST and 07:00 during AEDT. If a report must be ready by 07:00, it is late for half the year. Teams often "fix" this by editing the schedule twice a year, which is easy to forget.

Changeover nights

  • When clocks go forward (first Sunday in October in NSW, Victoria, the ACT, South Australia and Tasmania), local times from 02:00 to 02:59 do not exist. A job scheduled at 02:30 local time either runs at another time or is skipped, depending on the scheduler. Check your tool's documented behaviour, or avoid scheduling in that hour.
  • When clocks go back (first Sunday in April), 02:00 to 02:59 happens twice. A job in that hour may run twice. Avoid it, or make the job safe to run twice.
  • Queensland, the Northern Territory and Western Australia do not observe daylight saving. A schedule in Australia/Brisbane never shifts.

Doing it in common tools

Tool How to set a time zone
Azure Data Factory schedule trigger Choose the time zone on the trigger
Databricks Lakeflow Jobs Set the time zone on the job's schedule
Apache Airflow Use a time-zone-aware start_date or timetable
Polysync Each schedule has its own time zone; the editor shows a plain-English summary and the next three run times in that zone

In Polysync a task can carry several schedules, each with its own zone, for example a weekday 06:00 Sydney schedule and a month-end schedule.

Frequently asked questions

Should I schedule everything in UTC to be safe?

Only if the business does not care about local time. If the deadline is "before the 07:00 Sydney meeting", schedule in Sydney time.

How can I check a schedule across the changeover?

Look at the next run times your scheduler predicts around the first Sunday of April and October, or test the expression with a library that supports time zones.

Can one task follow two cities' business hours?

Yes, with two schedules in different time zones. Make sure the task is safe if both fire close together, for example by setting maximum concurrent runs to 1.

Microsoft, Azure, Azure Data Factory, Microsoft Fabric, Power BI, Logic Apps and Microsoft Marketplace are trademarks of the Microsoft group of companies. Apache Airflow and Airflow are trademarks of the Apache Software Foundation. Databricks and Lakeflow are trademarks of Databricks, Inc. All other product names are the property of their respective owners and are used for identification only. No endorsement by their owners is implied.

Data pipeline orchestration for Azure-first teams

Keep your ADF, Databricks, Fabric and Power BI jobs. Polysync connects them with shared scheduling, cross-platform dependencies and one run history, including jobs on AWS and Google Cloud. No orchestration code to write.

Learn more about Polysync