# Alarm Acknowledgement

**URL:** <https://forum.inductiveautomation.com/t/alarm-acknowledgement/9288>\
**Category:** Ignition\
**Created:** [November 5, 2014, 12:43am UTC](https://forum.inductiveautomation.com/t/alarm-acknowledgement/9288 "2014-11-05T00:43:16Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![camatt3](https://avatars.discourse-cdn.com/v4/letter/c/22d042/32.png) [@camatt3](https://forum.inductiveautomation.com/u/camatt3)\
**Post date:** [November 5, 2014, 12:43am UTC](https://forum.inductiveautomation.com/t/alarm-acknowledgement/9288/1 "2014-11-05T00:43:16Z")

</div>

Hi,

Aim: enter the pipeline to begin notifying each user in the roster until it is acknowledged. If after a certain time period the alarm is still active, in effect unacknowledge the alarm and begin the pipeline process again.

Problem: it seems there is no method to unacknowledge an alarm. So instead, I tried to attach a custom ‘responseReceived’ property to the alarm event which could be set when an acknowledgment response is received (e.g. by email), and cleared after the certain time period. When ‘responseReceived’ is set, the ‘eventCanceled’ property should also be set to drop out of the notification pipeline. However, I haven’t managed to achieve the expected result for ‘eventCanceled’, as outlined in the user manual: [https://support.inductiveautomation.com/usermanuals/ignition/index.html?alarm\_properties.htm](https://support.inductiveautomation.com/usermanuals/ignition/index.html?alarm_properties.htm)

So, what I’d like to know is, how should the ‘eventCanceled’ property be used, or, is there a better way to achieve the desired result?

---

<div class="post-metadata">

**Author:** ![camatt3](https://avatars.discourse-cdn.com/v4/letter/c/22d042/32.png) [@camatt3](https://forum.inductiveautomation.com/u/camatt3)\
**Post date:** [November 5, 2014, 3:08am UTC](https://forum.inductiveautomation.com/t/alarm-acknowledgement/9288/2 "2014-11-05T03:08:51Z")

</div>

I just realised this won’t work anyway unless there is a way to edit the alarm event’s property outside of the pipeline. Is there?