# Alarm Notification Pipeline Runtime Properties

**URL:** <https://forum.inductiveautomation.com/t/alarm-notification-pipeline-runtime-properties/25943>\
**Category:** Ignition\
**Created:** [June 19, 2019, 2:30pm UTC](https://forum.inductiveautomation.com/t/alarm-notification-pipeline-runtime-properties/25943 "2019-06-19T14:30:24Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![dion.botha](https://avatars.discourse-cdn.com/v4/letter/d/46a35a/32.png) [@dion.botha](https://forum.inductiveautomation.com/u/dion.botha)\
**Post date:** [June 19, 2019, 2:30pm UTC](https://forum.inductiveautomation.com/t/alarm-notification-pipeline-runtime-properties/25943/1 "2019-06-19T14:30:25Z")

</div>

Hi Guys,

I am trying to use some [alarm properties](https://docs.inductiveautomation.com/display/DOC80/Alarm+Event+Properties+Reference) in my pipeline script block. I can get alarm event properties (e.g. `event.name`) and associated data (e.g. `event.asset_name`) but I can’t seem to work out how to get runtime properties - e.g. `event.ackUser` does not work.

---

<div class="post-metadata">

**Author:** ![dion.botha](https://avatars.discourse-cdn.com/v4/letter/d/46a35a/32.png) [@dion.botha](https://forum.inductiveautomation.com/u/dion.botha)\
**Post date:** [June 20, 2019, 5:31pm UTC](https://forum.inductiveautomation.com/t/alarm-notification-pipeline-runtime-properties/25943/2 "2019-06-20T17:31:20Z")

</div>

Anyone?

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [June 20, 2019, 5:46pm UTC](https://forum.inductiveautomation.com/t/alarm-notification-pipeline-runtime-properties/25943/3 "2019-06-20T17:46:44Z")

</div>

When you configure an alarm you designate up to 3 different pipelines: Ack, Active, and Clear.

Is the pipeline you’re trying to access this property in designated as an Ack pipeline for the alarm? Did you disable the Acknowledged dropout condition for that pipeline?

---

<div class="post-metadata">

**Author:** ![dion.botha](https://avatars.discourse-cdn.com/v4/letter/d/46a35a/32.png) [@dion.botha](https://forum.inductiveautomation.com/u/dion.botha)\
**Post date:** [June 20, 2019, 6:36pm UTC](https://forum.inductiveautomation.com/t/alarm-notification-pipeline-runtime-properties/25943/4 "2019-06-20T18:36:15Z")

</div>

Hi Kevin, yes to both your questions, see screenshots below:

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/2X/b/b205d44fcb0b4978166bc2236c01aad3a813d119.png)

![image](https://us1.discourse-cdn.com/inductiveautomation/original/2X/9/9cf729bcef8aa3f9a109e8c1a6554cd1654a46d8.png)

![image](https://us1.discourse-cdn.com/inductiveautomation/original/2X/2/2fb1ca98314e69b5c4c21bf6e836abcb68113498.png)

![image](https://us1.discourse-cdn.com/inductiveautomation/original/2X/f/ff11c4b9d5be066fb12398521e9312e672c8e53c.png)

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [June 20, 2019, 6:42pm UTC](https://forum.inductiveautomation.com/t/alarm-notification-pipeline-runtime-properties/25943/5 "2019-06-20T18:42:18Z")

</div>

What version of Ignition is this? You might need to call into support and let them have a look. A quick test I put together with a print statement in the script block was able to capture the event.ackUser from an ack via the vision alarm status table, but I was using the latest 8.0.x dev version.

---

<div class="post-metadata">

**Author:** ![dion.botha](https://avatars.discourse-cdn.com/v4/letter/d/46a35a/32.png) [@dion.botha](https://forum.inductiveautomation.com/u/dion.botha)\
**Post date:** [June 20, 2019, 7:19pm UTC](https://forum.inductiveautomation.com/t/alarm-notification-pipeline-runtime-properties/25943/6 "2019-06-20T19:19:50Z")

</div>

Hi Kevin, thanks for your input, we only have the basic care support contract (email support only so I usually try the forums first). We are currently running V7.9.9, so my pipelines are all still global and thus am not able to do a print statement… I am also acknowledging through the email link rather than the alarm status table… I just retried through the alarm status table - no difference. I am upgrading to V8 soon so maybe I will wait until then to see if it resolves itself.

At very least, its nice to know that `event.ackUser` is correct.

---

<div class="post-metadata">

**Author:** ![dion.botha](https://avatars.discourse-cdn.com/v4/letter/d/46a35a/32.png) [@dion.botha](https://forum.inductiveautomation.com/u/dion.botha)\
**Post date:** [June 20, 2019, 7:33pm UTC](https://forum.inductiveautomation.com/t/alarm-notification-pipeline-runtime-properties/25943/7 "2019-06-20T19:33:03Z")

</div>

Just tried with `event.ackUserName` which works - good enough for me!

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [June 20, 2019, 7:38pm UTC](https://forum.inductiveautomation.com/t/alarm-notification-pipeline-runtime-properties/25943/8 "2019-06-20T19:38:43Z")

</div>

It’s strange that AckUserName works because it’s a calculated property off of AckUser. Is it possible your script was not correctly handling the AckUser value, which is not a String but a QualifiedPath value?

---

<div class="post-metadata">

**Author:** ![dion.botha](https://avatars.discourse-cdn.com/v4/letter/d/46a35a/32.png) [@dion.botha](https://forum.inductiveautomation.com/u/dion.botha)\
**Post date:** [June 20, 2019, 7:43pm UTC](https://forum.inductiveautomation.com/t/alarm-notification-pipeline-runtime-properties/25943/9 "2019-06-20T19:43:06Z")

</div>

Ahhhh, thanks Kevin, changing that line of code to `user = str(event.ackUser)` resolved the issue!
