Orchestrator time + daylight savings hasn't updated

Daylight savings meant time went forward 1 hour. Orchestrator is behind 1 hour. I have updated Orchestrator and SQL Servers time to reflect the correct time, and still orchestrator is 1 hour behind for schedules etc.

Any advice?

There is a Timezone setting in Orchestrator Tenant settings, You can set your timezone accordingly.
Please refer the screenshot for the same

There is a standard time called UTC – Coordinated Universal Time or Universal Time Coordinated, which is not adjusted to reflect changes either to or from Daylight Saving Time.

By default,The time zone of the tenant set to UTC. The timezone list depends on the machine.
Just you need to set your specific region timezone.

Hey, thanks for the reply.

I had it set to UTC for London (we’re in the UK) and the triggers were still not reflecting this.

I changed it to a timezone 1 hour ahead incase that helped, but still no joy.

For example, a bot scheduled to run at 12pm is saying it will run in 35 minutes (current time: 12.25)

Please check what timezone have you set in the Triggers, Ie Triggers Timezone
It is recommended that the tenant and the Robots have the same time zone.

Ah - thank you. That’s solved it :slight_smile:

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.