# \[BUG\]Shelved Alarm Behavior

**URL:** <https://forum.inductiveautomation.com/t/bug-shelved-alarm-behavior/95595>\
**Category:** Ignition\
**Tags:** ignition81, vision\
**Created:** [September 5, 2024, 3:02pm UTC](https://forum.inductiveautomation.com/t/bug-shelved-alarm-behavior/95595 "2024-09-05T15:02:35Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![amarks](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/amarks/32/45610_2.png) [@amarks](https://forum.inductiveautomation.com/u/amarks)\
**Post date:** [September 5, 2024, 3:02pm UTC](https://forum.inductiveautomation.com/t/bug-shelved-alarm-behavior/95595/1 "2024-09-05T15:02:35Z")

</div>

Question about shelved alarms.

I have a handful of alarms that are shelved. If the alarm is active and acked when shelved, if it clears and then becomes active again what happens? Do I end up with an active unacked alarm that's just "hidden?" Is this alarm included in the `[System]Gateway/Alarming/Active and Unacked` tag?

---

<div class="post-metadata">

**Author:** ![amarks](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/amarks/32/45610_2.png) [@amarks](https://forum.inductiveautomation.com/u/amarks)\
**Post date:** [September 6, 2024, 1:58pm UTC](https://forum.inductiveautomation.com/t/bug-shelved-alarm-behavior/95595/2 "2024-09-06T13:58:02Z")

</div>

I tested this myself, and yes this is exactly what happens.

Memory tag to test:  
 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/3/c/3ca877b17129d4d5308609afbf84c28633d2a1d2.png)

Toggle the tag and the alarm appears in the table:

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/7/2/7283b040f55ab98fd8cfbbf2d86c3ab26c190268.png)

Ack the alarm:

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/0/f/0f2282bcd76b69c191c81226c9d63e754aa9aeca.png)

Check the system tag:  
 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/3/4/3410a2bc8fd40771376203859f78a82f03b18f5d.png)

Everything is as expected so far.

However, when I shelve the alarm, clear it and re-activate it you can see that it does not appear in the table but the Active and Unacked system tag counts the alarm.

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/e/0/e06f2bed64c625097b5371153da4e38d2a254279.png)

I would say that the Active and Acked and Active and Unacked count should not count shelved alarms because they are not "active."

---

<div class="post-metadata">

**Author:** ![amarks](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/amarks/32/45610_2.png) [@amarks](https://forum.inductiveautomation.com/u/amarks)\
**Post date:** [September 6, 2024, 3:00pm UTC](https://forum.inductiveautomation.com/t/bug-shelved-alarm-behavior/95595/3 "2024-09-06T15:00:47Z")

</div>

What's really weird is that the `HasActive`, `ActiveAckCount`, and `ActiveUnackCount` **do not** include the alarm when it is shelved, but the individual alarm's `IsActive` does count the alarm as active.

I think this is a bug, or at least an oversight that needs fixing. @paul-griffith

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/e/a/ea231ff8d508319a59f32f905411480fa5bade78.png)

---

<div class="post-metadata">

**Author:** ![dcortez](https://avatars.discourse-cdn.com/v4/letter/d/aeb1de/32.png) [@dcortez](https://forum.inductiveautomation.com/u/dcortez)\
**Post date:** [September 6, 2024, 6:36pm UTC](https://forum.inductiveautomation.com/t/bug-shelved-alarm-behavior/95595/4 "2024-09-06T18:36:41Z")

</div>

Hi @amarks, thanks for bringing this up.

Gateway System Tags under `Gateway/Alarming/` shouldn't include shelved alarms to their counts. I'll create a bug ticket for this issue.

Under tag properties and into the general alarm properties, `ActiveCount`, `ActiveUnackCount`, `ClearUnackCount`, and `HasActive` shouldn't include shelved alarms either which is behaving as expected. When an alarm is shelved, then the `ShelvedCount` value should increment.

Finally, past the general alarm properties and deeper into the alarm's properties, these properties should indicate the actual state of the most recent alarm event. Alarm events still occur but if the alarm is shelved, then `isShelved` must be true as well.

Please let me know if this addresses all of your concerns or if I may have missed something.