KBI 311655 Issue Addressed: Delayed Daughter Offline Event Was Not Fired


Argent Advanced Technology 5.1A-1804-A or above


Tuesday, 24 April 2018


Argent Advanced Technology can be configured to fire internal Events for offline Daughter Engines

In order not to fire such an Event for a temporary condition, for example, Daughter Engine go offline than come back 30 seconds later, the seconds to delay firing Event can be specified

However, when this feature is used, the Event might not be fired in the end

The following line could be seen in the service log

The issue has been addressed in Argent Advanced Technology 5.1A-1804-B

Technical Background

The issue is caused by coding error

Internal Event has an internal time stamp for delayed Events

The timestamp is the time that the Event should be fired if the condition has not been corrected

The Engine mistakenly replaces existing internal Event of offline Daughter Engine with new ones without keeping the timestamp value

As a result, the Event is kept pushing to the future to fire

In some combination, the Event might not be fired at all

When the condition is corrected, the event is simply discarded as transient Event


Upgrade to Argent Advanced Technology 5.1A-1804-B or above

For customers who cannot upgrade immediately, consider resetting the Event delay seconds to zero