How Transitioning to or from Daylight Savings Time Affects Scheduled Tasks
The scheduled tasks in Integration Server are not skipped or repeated because of transitions to and from Daylight Saving Time (DST).
When transitioning to DST, the system clock time is advanced by one hour. However,
Integration Server will not skip the scheduled tasks that were scheduled to be run during the hour that is skipped because of transitioning to DST. If a task was scheduled to run in the hour that was skipped,
Integration Server will run the task in the ensuing hour. For example, if you have scheduled a task to run at 1:30:00 a.m. and if system clock time transitions to DST at 1:00:00 a.m.,
Integration Server will process the task at 2:30:00 a.m. system clock time.
When transitioning from DST, the system clock time is set back one hour. However, if
Integration Server has already executed a task in the hour before the change from DST to standard time,
Integration Server does not repeat that task again when the hour is repeated because of transitioning from DST. For example, if a task is executed at 1:30:00 a.m. and if the system clock time transitions to DST at 2:00:00 a.m., which sets the clock back to 1:00:00 am,
Integration Server does not process the task again at 1:30:00 a.m.
The simple and complex repeating tasks are unaffected by the transitions to and from DST.
Integration Server processes the repeating tasks at the specified intervals. That is, if a task is scheduled to run every hour,
Integration Server will execute the task at hourly intervals regardless of the system clock time.