US DST Fall Change Caused Scheduled Task on Gateway to NOT Execute
Article ID: 419411
Updated On:
Products
Issue/Introduction
For timezone where the US Daylight Saving Time is observed, at the clock reset in the fall, the system clock is reset to an hour back. That is 2am becomes 1am during the early hours of that day. As such, Gateway scheduled tasks scheduled to run hourly that fall within 1-3 am will miss their execution during the hour of 2-3am.
Environment
Release: 11.x
Component: CA APIM
Cause
It is because the hour of 2-3am becomes 1-2am on that day. In other words, there are two occurrences of 1-2am but the job scheduled was not supposed to run twice and hence on the day when the fall time changes occurred, the jobs that are supposed to execute hourly will not execute as the Gatewy engine will consider them executed an hour ago already. This is a known limitation of the scheduling library used in Gateway:
Avoid Scheduling Jobs Near the Transition Hours of Daylight Savings Time
Resolution
The standard recommendation by the scheduling library used in the Gateway suggests
Avoid Scheduling Jobs Near the Transition Hours of Daylight Savings Time
One possible workaround is, however, to set the system time to one of the timezone that does not observe the Daylight Saving Time. For example, the states of Hawaii and Arizona do not observe the DST.
Feedback
