# System.alarm.shelve(path, \[timeoutSeconds\], \[timeoutMinutes\]) script stop working in ignition 8.3 **URL:** \ **Category:** Ignition\ **Tags:** scripting\ **Created:** [January 21, 2026, 7:46pm UTC](https://forum.inductiveautomation.com/t/system-alarm-shelve-path-timeoutseconds-timeoutminutes-script-stop-working-in-ignition-8-3/113460 "2026-01-21T19:46:15Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![Eric\_Li](https://avatars.discourse-cdn.com/v4/letter/e/9d8465/32.png) [@Eric\_Li](https://forum.inductiveautomation.com/u/Eric_Li)\ **Post date:** [January 21, 2026, 7:46pm UTC](https://forum.inductiveautomation.com/t/system-alarm-shelve-path-timeoutseconds-timeoutminutes-script-stop-working-in-ignition-8-3/113460/1 "2026-01-21T19:46:15Z")
It looks like our shelve script stopped working after upgrading to Ignition **8.3**. The alarm is not being moved to the shelved table in the Alarm Status, and `isShelved()` always returns **false**. I’ve confirmed that the path format is correct, as I’m directly copying it from the source on **Alarm Status** **Table**. Is there anything else in **8.3** that could be causing this behavior? ---
**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\ **Post date:** [January 21, 2026, 8:07pm UTC](https://forum.inductiveautomation.com/t/system-alarm-shelve-path-timeoutseconds-timeoutminutes-script-stop-working-in-ignition-8-3/113460/2 "2026-01-21T20:07:38Z")
Where are you issuing the call from (client/designer vs gateway scope)? Are you trying to shelve alarms on a local provider, or a remote provider over the gateway network? Are there any errors in the logs? Does shelving from one of the alarm status table components (Vision or Perspective) work? ---
**Author:** ![Eric\_Li](https://avatars.discourse-cdn.com/v4/letter/e/9d8465/32.png) [@Eric\_Li](https://forum.inductiveautomation.com/u/Eric_Li)\ **Post date:** [January 21, 2026, 9:36pm UTC](https://forum.inductiveautomation.com/t/system-alarm-shelve-path-timeoutseconds-timeoutminutes-script-stop-working-in-ignition-8-3/113460/4 "2026-01-21T21:36:57Z")
Hey Paul, I ran the script in the Designer’s Script Console. Please see the attached screenshot for more details. The alarm tags exist on the same gateway’s tag server, so I assumed it should be treated as a local provider. ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/7/5/75a401bcfa2da8149c2e047bc20b028781832b5d.png) ---
**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\ **Post date:** [January 21, 2026, 10:10pm UTC](https://forum.inductiveautomation.com/t/system-alarm-shelve-path-timeoutseconds-timeoutminutes-script-stop-working-in-ignition-8-3/113460/5 "2026-01-21T22:10:24Z")
Okay, what about the rest of my questions 😃 1. Any errors in the gateway logs? 2. Does either 'alarm status table' component work to shelve alarms? ---
**Author:** ![Eric\_Li](https://avatars.discourse-cdn.com/v4/letter/e/9d8465/32.png) [@Eric\_Li](https://forum.inductiveautomation.com/u/Eric_Li)\ **Post date:** [January 21, 2026, 11:09pm UTC](https://forum.inductiveautomation.com/t/system-alarm-shelve-path-timeoutseconds-timeoutminutes-script-stop-working-in-ignition-8-3/113460/6 "2026-01-21T23:09:29Z")
Hey Paul, 1. There isn’t any related errors on gateway 2. Both shelve buttons on Alarm Status Table cannot shelve these four alarms in the previous screenshots That said, when I generate a new alarm and try to shelve it, both the script and the Shelve button work as expected. I suspect the alarms (in the first screenshots)that previously could not be shelved were caused by a data storage issue. ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/4/7/47f15a0e60b0b604b0cd428ee0bf0b46bfc9ac2b.png) ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/0/1/014c6233a69882a3da1fbe0a3eae11cb53b06f33.png) ---
**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\ **Post date:** [January 21, 2026, 11:19pm UTC](https://forum.inductiveautomation.com/t/system-alarm-shelve-path-timeoutseconds-timeoutminutes-script-stop-working-in-ignition-8-3/113460/7 "2026-01-21T23:19:32Z")
Got it - okay, if it's just these four alarms that refuse to be shelved (rather than the process of shelving in general being broken) then that's a generally positive sign. Though, obviously something is still wrong. If you're willing to troubleshoot further, I'd encourage you to contact our support department at this point. They might be able to help collect some information we can use to figure out what's gone wrong here. If you just want to get things moving, you could try shutting off the gateway, removing the `.alarms_$someNumbers` file in the gateway's data directory, and restarting it. That will clear out persisted alarm state data and start you from scratch, hopefully clearing out these issues. ---
**Author:** ![Eric\_Li](https://avatars.discourse-cdn.com/v4/letter/e/9d8465/32.png) [@Eric\_Li](https://forum.inductiveautomation.com/u/Eric_Li)\ **Post date:** [January 21, 2026, 11:36pm UTC](https://forum.inductiveautomation.com/t/system-alarm-shelve-path-timeoutseconds-timeoutminutes-script-stop-working-in-ignition-8-3/113460/8 "2026-01-21T23:36:11Z")
Sounds great. Thank you very much for your help!