# \[Bug\] Cannot shelve alarms from a remote tag provider with capital letters in the name

**URL:** <https://forum.inductiveautomation.com/t/bug-cannot-shelve-alarms-from-a-remote-tag-provider-with-capital-letters-in-the-name/79563>\
**Category:** Ignition\
**Tags:** perspective\
**Created:** [September 25, 2023, 3:12am UTC](https://forum.inductiveautomation.com/t/bug-cannot-shelve-alarms-from-a-remote-tag-provider-with-capital-letters-in-the-name/79563 "2023-09-25T03:12:23Z")\
**Posts on this page:** 4\
**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 25, 2023, 3:12am UTC](https://forum.inductiveautomation.com/t/bug-cannot-shelve-alarms-from-a-remote-tag-provider-with-capital-letters-in-the-name/79563/1 "2023-09-25T03:12:23Z")

</div>

**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 spoke gateways.
- This only occurs when the tag provider names for the spoke gateways include capital letters.
- Tested on several gateway versions 8.1.x up to 8.1.30
- Tested on Google Chrome, Microsoft Edge, and Perspective Workstation clients
- Tested with both full Ignition gateways and Ignition Edge gateways on the spokes.

**Related posts**

> [@Supress repeat instances of shelved alarm](https://forum.inductiveautomation.com/t/supress-repeat-instances-of-shelved-alarm/63754):
>
> 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.

> [@Shelved Alarms Keep Alarming When Re-triggered](https://forum.inductiveautomation.com/t/shelved-alarms-keep-alarming-when-re-triggered/52140/4):
>
> I believe this is a known bug. My org has implemented a workaround.

---

<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 25, 2023, 10:14am UTC](https://forum.inductiveautomation.com/t/bug-cannot-shelve-alarms-from-a-remote-tag-provider-with-capital-letters-in-the-name/79563/2 "2023-09-25T10:14:05Z")

</div>

Great bug report. You should submit it as an actual bug. (This forum is not support. Open a ticket at [https://support.inductiveautomation.com/](https://support.inductiveautomation.com/) instead.)

---

<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:17am UTC](https://forum.inductiveautomation.com/t/bug-cannot-shelve-alarms-from-a-remote-tag-provider-with-capital-letters-in-the-name/79563/3 "2023-09-25T10:17:30Z")

</div>

> [@pturmel](#):
>
> Great bug report

Agreed; it is excellent, and I hope [my original post](https://forum.inductiveautomation.com/t/supress-repeat-instances-of-shelved-alarm/63754/7) didn't come across the wrong way. Sometimes people don't realize that the forum is mostly just other developers that volunteer to help out. We aren't official.

---

<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 25, 2023, 10:54am UTC](https://forum.inductiveautomation.com/t/bug-cannot-shelve-alarms-from-a-remote-tag-provider-with-capital-letters-in-the-name/79563/4 "2023-09-25T10:54:33Z")

</div>

> [@justinedwards.jle](#):
>
> didn't come across the wrong way

Not a problem. I just saw and replied to this before I saw your comment on the other.