# How to re-evaluate (all) alarm property expressions

**URL:** <https://forum.inductiveautomation.com/t/how-to-re-evaluate-all-alarm-property-expressions/29385>\
**Category:** Ignition\
**Created:** [October 25, 2019, 6:56am UTC](https://forum.inductiveautomation.com/t/how-to-re-evaluate-all-alarm-property-expressions/29385 "2019-10-25T06:56:16Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![nminchin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nminchin/32/6911_2.png) [@nminchin](https://forum.inductiveautomation.com/u/nminchin)\
**Post date:** [June 20, 2025, 5:31am UTC](https://forum.inductiveautomation.com/t/how-to-re-evaluate-all-alarm-property-expressions/29385/2 "2025-06-20T05:31:24Z")

</div>

I'm running into this again, where I have a script to pull the alarm config for all alarms in the system, but for the alarms that have never come on, their alarm props like "activePipeline" are blank where they are actually bound to a UDT Parameter which is non-blank... I'm not sure what I can do to evaluate all of the alarm's props.

Edit:You just need to "restart" the tags at the lowest level and this evaluates these props. Thanks @pturmel!

> [@Re-Trigger Alarm Associated Data Property Bindings](https://forum.inductiveautomation.com/t/re-trigger-alarm-associated-data-property-bindings/95611/5):
>
> Bindings on alarm properties only evaluate on tag restart or an actual alarm event. A binding that controls alarm enable will only be evaluated on an alarm state change, and there will be no more state changes once disabled. The general alternative is to use a separate expression tag to compute the enable state, and use a valueChange event on that expression tag to write to the affected alarms.

---

_[View the full topic](https://forum.inductiveautomation.com/t/how-to-re-evaluate-all-alarm-property-expressions/29385)._