search cancel

Daylight Saving Time issues


Article ID: 90206


Updated On:


CA Automic Workload Automation - Automation Engine


Daylight Saving Time issues


Release: AOATAM99000-8.0-Automic-One Automation Tools-Application Manager


Detailed Description and Symptoms

Whenever Daylight Saving Time changes happen, there are many questions regarding how Automic handles the change and if there are any known issues that might arise during or after the change. There is information in the Automic documentation regarding how Automic reacts to time changes from Daylight Saving Time to Standard Time which can be found under Inside Automic Guide, Date and Time, Changing from Normal Timeto Daylight Savings Time.

There have been issues in the past with the Daylight Saving Time change, but as far as Automic is aware, all of these have been fixed. Please see the information below regarding these issues. These can also be found at by choosing the corresponding Application and Version (Automic Automation Engine for 9.OOA and Automic Operations Manager for 6.OOA and 8.OOA).




Automic Operations Manager ?8.00A 

Fixed in 8.00A Service Pack 2 (AutomationEngine hotfix 8.00A122-125)


18.08.2011 | 8.00A SP 2 Clock change to normal time also affects the period turnaround of active Schedules.


Error description:
Switching from daylight saving time to normal time (setting the time ahead in Spring) has the effect that the period turnaround of active Schedules is also set ahead for this period (per TimeZone). For example, if the clock is set ahead from 00:00 to 01:00, the period turnaround that was originally scheduled between 0:00 and 0:59 now takes takes place at exactly 01:00.
End all Schedules after you have changed the clock and restart them.




Automic Operations Manager 8.00A
Fixed in 8.00A Service Pack 1 (AutomationEngine hotfix 8.00A117-821)


09.05.2011 | 8.00A SP 1 DST changeover to standard time causes erroneous start time for recurring objects.
Error description:
Changing the daylight savings time over to standard time (winter time - the clock is set back for one hour), the system does not change the next scheduled start time of recurring tasks. As a result, no recurring tasks start for a period of one hour. The tasks are executed in the specified interval only when when the old start time is reached or exceeded.


PLEASE NOTE: If you are running Recurring tasks in your system, this may cause a System Outage.

For example:
The object SCRI.TEST starts on 31.10.10 at 2:20 (recurringly, every 10 minutes).
At 3:00 o'clock, the clock is set back for one hour (to 2:00). The next scheduled start time, however, remains 3:00. Therefore, the system does not start tasks between 2 and 3 o'clock.
2:30, 2:40, 2:50 (clock change), 2:00, 2:10, 2:20, 2:30, 2:40, 2:50, 3:00, 3:10
2:30, 2:40, 2:50 (clock change), 3:00, 3:10...
Not available
Automic Operations Manager 6.00A
Fixed in Server hotfix 6.00A015-201
09.07.2010 | 6.00A015-201 Changeover to summer time / winter time in TimeZone objects had the effect that the period turnaround of Schedules took place an hour late or early.
Error description:
The changeover to summer time or winter time in TimeZone objects was not considered for the period turnaround of Schedule objects. Thus, the period turnaround took place an hour late (summer time) or early (winter time). Restarting the Schedule solved this problem.
Use a Server version other than 6.00A005-402 (older or newer) because the problem does not occur there.

If it is not possible to apply this Hotfix before the next summer time/winter time changeover takes place, Automic recommends restarting all Schedule objects immediately after the change, or at latest before the next period turnaround takes place. Start Schedules with a logical date a day before or determine 00:00 or later for the period turnaround.


Please contact Automic Support if you have any questions. Thank you.