Clear events that shouldn't exist

We recently noticed in some of our production environments that there are several cleared state events with no associated active event. These events all appeared at the same time, one for each tag we had alarms configured for, including alarms that were disabled, this happened several times during the course of the last weeks.

The issue is similar to some others already in this forum:

  1. Orphaned Alarm Event Data in datasource alarm_events table
  2. Multiple instances of one alarm event without transition to any other
  3. Alarm Cleared but Never Active - #4 by jacob.ramirez
    However we did not recently update Ignition's version (which is currently 8.1.37), nor modified UDTs.

From the data provided by the historian, we were able to verify that the alarms should have never been active, meaning the issue is not about active events missing, but rather about cleared events seemingly appearing out of nowhere.

There seems to be a weak correlation between these events appearing and gateway restarts, however sometimes they appear without the gateway restarting, sometimes they don't appear despite the gateway restarting.

We can confirm the clear events are present in the database as well:

Can these events be safely ignored, or are they caused by something specific?

2 Likes

I found that I can safely ignore them and not really notice any adverse issues. As long as you use the system functions to handle any alarm events you shouldn’t really have any problems.

One of the mechanisms I found that can cause orphaned clear events is cycling the “Alarms Eval Enabled” from false to true; however, it gives me an event flag of 28, not 16, as shown in the image of your query.

16 seems like a normal clear event where as 28 is some form of system acknowledgement.

I haven’t seen any orphaned 16 flags so that might be some weird other issue.

Hopefully that adds some context

1 Like