We've recently seen a behaviour in ESP that we would like further clarification.
On Sunday, December 5th, 2021 we had an event (ESP.EVENT) scheduled as follows, with a calendar entry OUTAGES for December 5th:
SCHEDULE AT 00.30 ON OUTAGES STARTING SUN 5TH JAN 2021
December 5th was the last calendar entry for a special day called OUTAGES. An event error was generated and ESP suspended the ESP.EVENT event. This is expected behavior as ESP did not find any future dates for that special day. After adding a placeholder entry for OUTAGES on Jan 1st 2041, the event was resumed but the next scheduled date remained 00.30 on Sunday December 5th 2021.
Later when ESP event scan process ran at 06:00AM Tuesday morning, ESP triggered the event ESP.EVENT. This caused an unscheduled outage.
We would like to confirm if this is expected behaviour, if so, can you please explain the ESP logic that would cause an event with a past 'next scheduled date' value to be triggered following an event scan.
Release : 12.0
Component : ESP WORKLOAD AUTOMATION
To avoid this situation, We recommend to use the 'RESCHEDULE' operand when defining additional special day date. This option reschedules the events that use the special day and so the event would be ignored at scan time, since its schedule is far in the future.
For an Event using the specified calendars, adjust the schedule to account for changes to any calendar used by the Event.
If you don't specify RESCHEDULE, the schedule adjustment is done after the Event is manually triggered or runs according to the original schedule.
Using DEFSPEC to define a new special day.