When creating a trigger using Non-working days restrictions, I’ve previously read that the timezone of the trigger must match the timezone of the Orchestrator.
Upon upgrading to 2023.10.6 it now appears to be possible to select any timezone when using Non-working days restrictions but I am hesitant on how the trigger will behave.
Does anyone have experience with this?
The job will trigger according to the time zone selected in the dropdown. It will not trigger on the dates specified in the non-working days calendar.
There are no changes; everything is functioning as expected.
Hope you understand!!
Will the non-working days be defined using the trigger timezone or the timezone of the Orchestrator?
There are 9 hours difference between the trigger and Orchestrator timezone.
16.15 (UTC +00:00) will be 01:15 (UTC +09:00) - the following day.
Those non working days will work under Trigger time zone not the Orchestrator time zone… @theodore.henderson
Hope you understand!!
I hope you find the solution, If yes Make my post Mark as solution to close the loop… @theodore.henderson
Happy Automation!!
you might need to note that the timezone of trigger should not be set on non working days
cheers
This was also my understanding from the documentation. However, you can see from my initial screenshot that I have been able to successfully create a trigger, using a non-working days calendar, in a timezone that is not the same as the Orchestrator.
you can but it would not take effect mostly…you can just confirm the same by setting the date of trigger
cheers
Anil_G
V_Roboto_V
mkankatala
ashokkarale
sharazkm32
Somanath1
Sai17
Jon_G
Sonadri_Tanaya_Mishra_EXT
harsh.savaliya