Foglight is ignoring rule delay firing behavior as defined in the Alarm & Action Behaviors tab (4247278)

Foglight is ignoring rule delay firing behavior as defined in the Alarm & Action Behaviors tab

A Data Driven rule has been configure to have a 30 min delay and is set to only fire after the second failure.  Foglight is ignoring these settings and firing this rule immediately after the rule condition is met.

The 30 minute setting in the behaviors tab applies only to the first evaluation of the rule after the FMS has been restarted. Subsequent evaluations will not adhere to the 30 minute delay setting in the Behaviors tab.

This means that users can only expect the 30 minute delay after an FMS restart or after the rule has been edited.  After that there is no 30 minute delay.

Modify the rule to a Time Driven rule (from Data Driven), and be configured to fire after x consecutive positive valuations. 

Example:  For a 30 min delay, and the rule evaluates every 5 minutes, set the behavior to fire after 6 consecutive "true" evaluations.

BACKGROUND A time-driven trigger causes one or more of a rule’s conditions to be evaluated once per pre-defined interval. By default, time-driven rules are only evaluated if data for the evaluation of the condition is available, but users can override this behavior, if required. For Time-driven triggers only. Under Rule Triggering, select the Time Driven option. Specify the recurrence interval for the trigger in the hh:mm:ss format.     To evaluate the rule conditions on each interval, regardless of the existence of data, select Enable Trigger Without Data. • Triggers: The total number of times that the rule conditions evaluated the object instance.    • Fired: The total number of times that the rule changed the state. • Hit: The total number of times that the rule conditions evaluated to True.