# "Shelve" alarm for 5 minutes after notification

**URL:** <https://forum.inductiveautomation.com/t/shelve-alarm-for-5-minutes-after-notification/64687>\
**Category:** Ignition\
**Tags:** ignition81, scripting\
**Created:** [September 29, 2022, 8:18pm UTC](https://forum.inductiveautomation.com/t/shelve-alarm-for-5-minutes-after-notification/64687 "2022-09-29T20:18:13Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![markusx1094](https://avatars.discourse-cdn.com/v4/letter/m/77aa72/32.png) [@markusx1094](https://forum.inductiveautomation.com/u/markusx1094)\
**Post date:** [September 29, 2022, 8:18pm UTC](https://forum.inductiveautomation.com/t/shelve-alarm-for-5-minutes-after-notification/64687/1 "2022-09-29T20:18:13Z")

</div>

I need to be able to have my alarms not notify for 5 minutes after the initial notification. I would still want the alarm to be visible on the screen but just so it doesn't send a notification out until the delay has passed. I tried using system.alarm.shelve but it didn't show in the shelved section of the alarm status table so that wouldn't work unless you could make it show there. Is there a good way to do this with the notification pipeline or would this be something that one would have to implement in the PLC before it ever reaches Ignition.

---

<div class="post-metadata">

**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:** [September 29, 2022, 8:31pm UTC](https://forum.inductiveautomation.com/t/shelve-alarm-for-5-minutes-after-notification/64687/2 "2022-09-29T20:31:58Z")

</div>

In an alarm pipeline, you can directly add a Delay block before your Notification block:  
[https://docs.inductiveautomation.com/pages/viewpage.action?pageId=72419404#PipelineBlocks-DelayBlock](https://docs.inductiveautomation.com/pages/viewpage.action?pageId=72419404#PipelineBlocks-DelayBlock)

Or, if you think there's a chance multiple alarms could enter the same pipeline within a given timespan, you could set up Consolidation on the notification block:  
[https://docs.inductiveautomation.com/display/DOC81/Notification+Block#NotificationBlock-Consolidation](https://docs.inductiveautomation.com/display/DOC81/Notification+Block#NotificationBlock-Consolidation)

---

<div class="post-metadata">

**Author:** ![markusx1094](https://avatars.discourse-cdn.com/v4/letter/m/77aa72/32.png) [@markusx1094](https://forum.inductiveautomation.com/u/markusx1094)\
**Post date:** [September 30, 2022, 1:38pm UTC](https://forum.inductiveautomation.com/t/shelve-alarm-for-5-minutes-after-notification/64687/3 "2022-09-30T13:38:58Z")

</div>

Yep, I plan on using consolidation for some of the alarms but I talked with my boss and we agreed that rather than making some workaround to stop alarm floods lets just do it right. Thank you for your help though.
