# Supress repeat instances of shelved alarm

**URL:** <https://forum.inductiveautomation.com/t/supress-repeat-instances-of-shelved-alarm/63754>\
**Category:** Ignition\
**Tags:** ignition81\
**Created:** [September 5, 2022, 6:30am UTC](https://forum.inductiveautomation.com/t/supress-repeat-instances-of-shelved-alarm/63754 "2022-09-05T06:30:44Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Douglas\_Lawrie](https://avatars.discourse-cdn.com/v4/letter/d/a87d85/32.png) [@Douglas\_Lawrie](https://forum.inductiveautomation.com/u/Douglas_Lawrie)\
**Post date:** [September 5, 2022, 6:30am UTC](https://forum.inductiveautomation.com/t/supress-repeat-instances-of-shelved-alarm/63754/1 "2022-09-05T06:30:44Z")

</div>

After shelving an alarm, I want repeat instances of the alarm to be treated as shelved until the shelving time has elapsed. The default behaviour seems to be to shelve a single instance of an alarm but future instances of that alarm still appear in the alarm status table.

Is this supported?

Edit: The documentation says repeat instances of a shelved alarm should be ignored but that does not seem to be happening in my case for some reason.

---

<div class="post-metadata">

**Author:** ![obober](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/obober/32/67865_2.png) [@obober](https://forum.inductiveautomation.com/u/obober)\
**Post date:** [September 15, 2022, 5:58pm UTC](https://forum.inductiveautomation.com/t/supress-repeat-instances-of-shelved-alarm/63754/2 "2022-09-15T17:58:47Z")

</div>

According to the documentation under [Alarm Shelving](https://docs.inductiveautomation.com/display/DOC81/Alarming#Alarming-AlarmShelving), the expected behavior is that repeat instances of a shelved alarm are simply ignored. Are you asking to have that ignored alarm also get shelved? If so, may I ask why? Are you looking to see the number of times that the alarm went off while there was a shelved instance of it?

---

<div class="post-metadata">

**Author:** ![Douglas\_Lawrie](https://avatars.discourse-cdn.com/v4/letter/d/a87d85/32.png) [@Douglas\_Lawrie](https://forum.inductiveautomation.com/u/Douglas_Lawrie)\
**Post date:** [September 19, 2022, 1:03am UTC](https://forum.inductiveautomation.com/t/supress-repeat-instances-of-shelved-alarm/63754/3 "2022-09-19T01:03:50Z")

</div>

Our alarm status table seems to be showing repeat instances of shelved alarms. I.e. there is an entry in the Shelved tab, and multiple occurrences in the Active tab (see screenshots).

 ![shelved](https://us1.discourse-cdn.com/inductiveautomation/original/3X/0/1/01a78cd7f6332f648bb2f258415e132fdb106a0a.jpeg)  
 ![active](https://us1.discourse-cdn.com/inductiveautomation/original/3X/2/4/24ad59bd2e515b9d29991251d07d11f69701f0d2.jpeg)

---

<div class="post-metadata">

**Author:** ![Douglas\_Lawrie](https://avatars.discourse-cdn.com/v4/letter/d/a87d85/32.png) [@Douglas\_Lawrie](https://forum.inductiveautomation.com/u/Douglas_Lawrie)\
**Post date:** [September 23, 2023, 4:26am UTC](https://forum.inductiveautomation.com/t/supress-repeat-instances-of-shelved-alarm/63754/4 "2023-09-23T04:26:51Z")

</div>

I have worked through this with iControls in Australia and found a workaround.

It turns out, this bug only exists when trying to shelve an alarm on a remote tag provider, whose source tag provider has capital letters in the name 🙄

**Changing the spoke tag provider names to snake\_case in our hub/spoke gateway architecture solved the problem**. This was a pain in the neck for our large Ignition installation because tag providers are referenced everywhere, but ultimately resolved the issue.

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [September 23, 2023, 2:03pm UTC](https://forum.inductiveautomation.com/t/supress-repeat-instances-of-shelved-alarm/63754/5 "2023-09-23T14:03:20Z")

</div>

> [@Douglas\_Lawrie](#):
>
> this bug

Sounds worth a formal bug report. That is certainly surprising behavior.

---

<div class="post-metadata">

**Author:** ![Douglas\_Lawrie](https://avatars.discourse-cdn.com/v4/letter/d/a87d85/32.png) [@Douglas\_Lawrie](https://forum.inductiveautomation.com/u/Douglas_Lawrie)\
**Post date:** [September 25, 2023, 3:12am UTC](https://forum.inductiveautomation.com/t/supress-repeat-instances-of-shelved-alarm/63754/6 "2023-09-25T03:12:58Z")

</div>

Created this bug report 🙂

> [@\[Bug\] Cannot shelve alarms from a remote tag provider with capital letters in the name](https://forum.inductiveautomation.com/t/bug-cannot-shelve-alarms-from-a-remote-tag-provider-with-capital-letters-in-the-name/79563):
>
> Unexpected behaviour When shelving an alarm from a perspective alarm status table, the alarm entry moves from the Active tab to the Shelved tab, but when the alarm retriggers, new instances appear in the active tab. Expected behaviour Shelved alarms do not show as Active until the shelving time elapses. Other details This only occurs in our hub/spoke gateway architecture, where perspective clients are connected to the hub gateway and alarms are coming via remote tag providers from the spok…

---

<div class="post-metadata">

**Author:** ![justinedwards.jle](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/justinedwards.jle/32/37854_2.png) [@justinedwards.jle](https://forum.inductiveautomation.com/u/justinedwards.jle)\
**Post date:** [September 25, 2023, 10:09am UTC](https://forum.inductiveautomation.com/t/supress-repeat-instances-of-shelved-alarm/63754/7 "2023-09-25T10:09:24Z")

</div>

This is not an official bug report. What you need to do is [contact support](https://support.inductiveautomation.com/hc/en-us) and report it to them. They can then open an official ticket on this.
