There is an issue with scheduling Runbooks that start with the Monitor Date/Time activity during DST.
Daylight Saving Time (United States) 2012 began at 2:00 AM on Sunday, March 11. At this time,
the clocks would be moved ahead one hour to 3:00 AM.
- This means any Runbooks scheduled to run between the hours of 2:00 AM - 3:00 AM would be skipped entirely.
Daylight Saving Time (United States) 2012 ended at 2:00 AM on Sunday, November 4. At this time,
the clocks would be moved back one hour to 1:00 AM.
- This means any Runbooks schedule to run between the hours of 1:00 AM - 2:00 AM would run twice.
Depending on what the runbooks are executing, this could cause major issues and/or unscheduled downtime. It would also suggest Runbooks that are not set on an hourly interval (i.e. once daily) be scheduled outside of the hours of 1:00 AM - 3:00 AM to avoid any interruptions. Unless you throw an exception into the schedule to work around the timing that the clocks are changed.