Lingering web dev alarms

When I use the python function to acknowledge an alarm,


the alarm is acknowledged and disappears from the alarm status table, but it continues to be output by a call to the python function,

system.alarm.queryStatus(State=[“ActiveUnacked”,“ActiveAcked”,“ClearAcked”,“ClearUnacked”, includeShelved=“false”)

Although, it does show the alarm has been acknowledged, shouldn’t it disappear from there as well?

Acknowledge does not equal RESET.
The alarm will go from Active-Unacked to Active-Acked
Only when the underlying trigger for the alarm goes off will the alarm be removed from the active alarm system.
For more info.

1 Like