# Alarm clear delay expression working for one alarm but not for any others **URL:** \ **Category:** Ignition\ **Created:** [December 11, 2025, 10:06pm UTC](https://forum.inductiveautomation.com/t/alarm-clear-delay-expression-working-for-one-alarm-but-not-for-any-others/112775 "2025-12-11T22:06:02Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Kyle\_K](https://avatars.discourse-cdn.com/v4/letter/k/779978/32.png) [@Kyle\_K](https://forum.inductiveautomation.com/u/Kyle_K)\ **Post date:** [December 11, 2025, 10:06pm UTC](https://forum.inductiveautomation.com/t/alarm-clear-delay-expression-working-for-one-alarm-but-not-for-any-others/112775/1 "2025-12-11T22:06:02Z")
I am trying to setup some alarming where the alarm triggers when sensor value is outside a normal range and will delay clearing for X amount of time or when the latched alarm bit in the PLC is cleared. I got this to work with the high high alarm, but when I apply exactly the same settings to the low low alarm it doesn’t work. The low low alarm immediately clears once the sensor returns to a value above the low low setpoint. The screenshots below show how the high high and the low low alarms are setup. I can’t figure out why it works with the HH and not with the LL, to me they look like they are setup identically and should function the same. Can anyone see a reason why the LL alarm clears immediately? I am 100% sure that the Analyzer-LL tag latches in and stays at a value of 1 until the alarm reset command is given. ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/b/d/bd6d20d52ca8134c50a28aa020e8a684e3d54f5f.png) ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/d/b/db6741d7a8b5077d5682f9b1d6b0badf23c66470.png) ---
**Author:** ![ryan.white](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/ryan.white/32/73193_2.png) [@ryan.white](https://forum.inductiveautomation.com/u/ryan.white)\ **Post date:** [December 11, 2025, 11:18pm UTC](https://forum.inductiveautomation.com/t/alarm-clear-delay-expression-working-for-one-alarm-but-not-for-any-others/112775/2 "2025-12-11T23:18:24Z")
Have you confirmed that `{[.]Analyzer-LL}` is a non-zero value for the instance you are testing on? ---
**Author:** ![Kyle\_K](https://avatars.discourse-cdn.com/v4/letter/k/779978/32.png) [@Kyle\_K](https://forum.inductiveautomation.com/u/Kyle_K)\ **Post date:** [December 12, 2025, 2:21pm UTC](https://forum.inductiveautomation.com/t/alarm-clear-delay-expression-working-for-one-alarm-but-not-for-any-others/112775/3 "2025-12-12T14:21:20Z")
I have, its definitely a 1 when the alarm occurs ---
**Author:** ![MMaynard](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/mmaynard/32/3366_2.png) [@MMaynard](https://forum.inductiveautomation.com/u/MMaynard)\ **Post date:** [December 12, 2025, 3:07pm UTC](https://forum.inductiveautomation.com/t/alarm-clear-delay-expression-working-for-one-alarm-but-not-for-any-others/112775/4 "2025-12-12T15:07:59Z")
Nevermind, just realized that is a tag path and not a parameter. ---
**Author:** ![Kyle\_K](https://avatars.discourse-cdn.com/v4/letter/k/779978/32.png) [@Kyle\_K](https://forum.inductiveautomation.com/u/Kyle_K)\ **Post date:** [December 12, 2025, 3:35pm UTC](https://forum.inductiveautomation.com/t/alarm-clear-delay-expression-working-for-one-alarm-but-not-for-any-others/112775/5 "2025-12-12T15:35:57Z")
I think I figured out the problem, it was related to the timing between the alarm being triggered and the Analyzer-LL tag being read from the PLC. The alarm was being triggered in Ignition at the same time the Analyzer-LL tag was being set in the PLC. But there is a delay in Ignition reading that boolean value from the PLC, so the alarm was clearing before it had a chance to update the tag and do the clear delay calculation.