Alberta, Canada will be staying on DST time zone permanently this year. How to handle this in Orchestrator?

Alberta, Canada will be staying on DST time zone permanently this year. (UTC -06:00) How to handle this in Orchestrator?

Attached screen shot of the tenant time zone setting here:

@dkorenowski Hi, once Alberta moves to permanent UTC-06:00, the current Mountain Time (US & Canada) setting may no longer be suitable because it follows DST rules.

The ideal solution would be to select the new Alberta/permanent UTC-06:00 timezone once it is available in Orchestrator. Also make sure to update the timezone on existing Time Triggers separately, since trigger timezone is independent of the tenant timezone.

If the Alberta timezone is not available in the dropdown after the change, I would recommend raising a UiPath Support ticket rather than using another regional UTC-06:00 timezone as a permanent workaround.

Hi @dkorenowski

For Orchestrator, I would keep the tenant timezone as Mountain Time for now.

Since Alberta’s timezone rules are changing, UiPath should update the timezone definition accordingly. If the new UTC-06:00 behavior is not reflected after the change, raise a ticket with UiPath Support.

Also, check the timezone configured on the individual trigger, as it can have its own timezone setting.

Hi @dkorenowski ,
Use a fixed UTC-06:00 time zone instead of a DST-based Mountain Time zone whenever possible, and validate all schedules after the change.

Thanks

Hi @dkorenowski,

Welcome to the community.

As the change is planned for 26 Nov, you can update the Orchestrator timezone to UTC-06:00 on/before that date.

Also, check your triggers. If any are configured with UTC-07:00, change them to UTC-06:00 and verify that the triggers run at the expected time.

If this resolves your query, please mark the answer as the solution.

Thanks!

@dkorenowski
I’d keep Mountain Time for now and check whether UiPath or Windows updates the Alberta timezone definition when the change takes effect. Also review the timezone on every Time Trigger because it can be configured separately from the tenant timezone. If the correct Alberta or fixed UTC-06 option still isn’t available, I’d open a UiPath support ticket rather than use another region as a permanent workaround.