Around the daylight saving time switch, schedules and periodic objects kick off as thought the daylight savings time switch happened a week early or late:
During Autumn/Fall: Jobs kick off an hour later than they should beginning a week earlier than the daylight saving time switch
During Spring: Jobs kick off an hour earlier than they should beginning a week later than the daylight saving time switch
Release : 12.x
Component : AUTOMATION ENGINE
Incorrect definition on timezone object
Go into the client where the object is running incorrectly
Open the timezone object (if it does not exist in this client, then it will be in client 0)
If the issue happened in Autumn, check the "Revert to normal time" setting, being sure it is set to the correct week of the correct month
If the issue happened in Spring, check the "Change to daylight saving time on" setting, being sure it is set to the correct week of the correct month
If C_PERIOD objects were affected by the incorrect definition:
If Schedules were affected by the incorrect timezone definition, there are two options:
Information on defining timezone objects can be found in the documentation: https://docs.automic.com/documentation/webhelp/english/AA/12.3/DOCU/12.3/Automic%20Automation%20Guides/help.htm#AWA/Objects/obj_TimeZone.htm#link4