# Alarm setpoints occasionally show null in tag browser and view, but have correct value in tag diagnostics **URL:** \ **Category:** Ignition\ **Tags:** ignition81\ **Created:** [June 16, 2025, 1:51pm UTC](https://forum.inductiveautomation.com/t/alarm-setpoints-occasionally-show-null-in-tag-browser-and-view-but-have-correct-value-in-tag-diagnostics/107420 "2025-06-16T13:51:11Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![Alex.DeBate](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/alex.debate/32/72299_2.png) [@Alex.DeBate](https://forum.inductiveautomation.com/u/Alex.DeBate)\ **Post date:** [June 16, 2025, 1:51pm UTC](https://forum.inductiveautomation.com/t/alarm-setpoints-occasionally-show-null-in-tag-browser-and-view-but-have-correct-value-in-tag-diagnostics/107420/1 "2025-06-16T13:51:11Z")
This happens randomly. I've tried tracing this down to a root cause, but I can't find anything. The alarm setpoints are set via an expression, but any errors that might arise from that don't explain the discrepancy between the diagnostics and the tag browser. I've found that disabling and re-enabling the tag causes the issue to go away, but I'm hoping for a long-term fix. ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/2/0/208b903092776693b95243f7562bbce48d56c3b2.png) ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/e/7/e79c7e008066bcb823280a2ce97efeab01c17cfb.png) ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/c/0/c0bc3ea98c4508b91cb52b19e84890fd828d607e.png) ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/8/6/86e4533bc19ad85137dd542e5f95fc89a352bce7.png) ---
**Author:** ![amarks](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/amarks/32/45610_2.png) [@amarks](https://forum.inductiveautomation.com/u/amarks)\ **Post date:** [June 16, 2025, 1:53pm UTC](https://forum.inductiveautomation.com/t/alarm-setpoints-occasionally-show-null-in-tag-browser-and-view-but-have-correct-value-in-tag-diagnostics/107420/2 "2025-06-16T13:53:30Z")
What is the expression? ---
**Author:** ![Alex.DeBate](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/alex.debate/32/72299_2.png) [@Alex.DeBate](https://forum.inductiveautomation.com/u/Alex.DeBate)\ **Post date:** [June 16, 2025, 1:57pm UTC](https://forum.inductiveautomation.com/t/alarm-setpoints-occasionally-show-null-in-tag-browser-and-view-but-have-correct-value-in-tag-diagnostics/107420/3 "2025-06-16T13:57:53Z")
```python if({[.]MES/AX/Temperature} != 0, {[.]MES/AX/Temperature}, {[.]Temperature SP})*1.01 ``` From what I can tell, that this only happens when `{[.]MES/AX/Temperature}` is non-zero, but doesn't _always_ happen when it's non-zero. There is a similar expression for the low SP, just multiplied by 0.99 instead of 1.01. ---
**Author:** ![amarks](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/amarks/32/45610_2.png) [@amarks](https://forum.inductiveautomation.com/u/amarks)\ **Post date:** [June 16, 2025, 1:58pm UTC](https://forum.inductiveautomation.com/t/alarm-setpoints-occasionally-show-null-in-tag-browser-and-view-but-have-correct-value-in-tag-diagnostics/107420/4 "2025-06-16T13:58:51Z")
add a try catch or isNull. I'm guessing the tag quality may be causing an issue. If `[.]MES/AX/Temperature` is `null` it will return `null` because `null != 0` (I believe) ---
**Author:** ![amarks](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/amarks/32/45610_2.png) [@amarks](https://forum.inductiveautomation.com/u/amarks)\ **Post date:** [June 16, 2025, 2:06pm UTC](https://forum.inductiveautomation.com/t/alarm-setpoints-occasionally-show-null-in-tag-browser-and-view-but-have-correct-value-in-tag-diagnostics/107420/5 "2025-06-16T14:06:15Z")
Are you doing this expression binding directly in the alarm setpoint? I would do it in an expression tag outside this tag and just bind the alarm setpoint to that tag. ---
**Author:** ![Alex.DeBate](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/alex.debate/32/72299_2.png) [@Alex.DeBate](https://forum.inductiveautomation.com/u/Alex.DeBate)\ **Post date:** [June 18, 2025, 6:23pm UTC](https://forum.inductiveautomation.com/t/alarm-setpoints-occasionally-show-null-in-tag-browser-and-view-but-have-correct-value-in-tag-diagnostics/107420/6 "2025-06-18T18:23:04Z")
That seems to have fixed it, but I'm still surprised at the original issue. I'm going to throw a ticket in with support to see if this is in fact a bug. ---
**Author:** ![amarks](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/amarks/32/45610_2.png) [@amarks](https://forum.inductiveautomation.com/u/amarks)\ **Post date:** [June 18, 2025, 6:34pm UTC](https://forum.inductiveautomation.com/t/alarm-setpoints-occasionally-show-null-in-tag-browser-and-view-but-have-correct-value-in-tag-diagnostics/107420/7 "2025-06-18T18:34:45Z")
I think it has to do with how the alarm setpoint bindings work within the alarm setup itself. I would only ever direct bind to another tag. Don't count on it to do any evaluation.