During testing over the past few days of 7.6 new alarming I am seeing a behavior that I don’t think is correct. When setting up an alarm we use different “permissive” in the enable for different alarms. When we also set the active delay to some value other than 0 we get very unexpected behavior. When alarm is set this way and the value for the tag your are alarming on is in an alarm state and the enable goes high then low in less time than that set in the active delay value then the alarm goes active and hangs there even though the alarms enable property is not true at this time.
We tested this in a just memory tags and it does the same thing. Note this behavior is not seen if the active delay value is set to a 0.
Running 7.6 rc5