Daylight Saving Time issues

Daylight Saving Time (DST), also known as summer time, is a conventional local time adopted by many countries of the world on a seasonal basis. Most commonly, DST is obtained by adjusting the official local time forward, by one hour, for the spring, summer, and early autumn periods. These time changes might create issues when the following actions are performed:

  • Closing events during DST
  • Scheduling exclusions during DST

Closing events during DST

Daylight Savings Time (DST) can cause a delay of one hour when closing events. 

The required DST patches are not present on the operating system, which causes a delay of one hour in closing events. For example, when an event condition is triggered at 12:55 A.M., but the event gets triggered at 01:10 (there is a 15-minute duration defined in the threshold). 

After the event is triggered at 01:10, wait for a few minutes (for example, until 1:20) and snub the condition that caused the event. Doing this must close the event after 15 minutes, but the event is closed only when the clock strikes 01:20 for the second time.

Scheduling exclusions during DST

Do not schedule exclusions to occur during the hour that is lost when Daylight Savings Time (DST) begins or during the hour that is gained when it ends. 

You can create a faulty schedule using exclusion. Example: March 11, 2007, 03:30 A.M. to 03:10 A.M. Exclusion (where the from time is meant to be 02:30 A.M.). An extra hour of schedule is considered when the from time is before DST begins and the to time is within the hour gained when DST begins. For example: a schedule defined from 12:30 A.M. to 01:59 A.M. Exclusion, 12:30 A.M. to 1:59 A.M. PDT, and 01:00 A.M.to 01:59 A.M. of PST are considered.

Do not schedule exclusions to occur during the hour that is lost when DST begins in the spring or during the hour that is gained when DST ends in the fall.

Was this page helpful? Yes No Submitting... Thank you

Comments