# Notification bug or something else

**URL:** <https://forum.inductiveautomation.com/t/notification-bug-or-something-else/47389>\
**Category:** Ignition\
**Created:** [June 3, 2021, 11:19am UTC](https://forum.inductiveautomation.com/t/notification-bug-or-something-else/47389 "2021-06-03T11:19:29Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![ltraverso](https://avatars.discourse-cdn.com/v4/letter/l/e56c9b/32.png) [@ltraverso](https://forum.inductiveautomation.com/u/ltraverso)\
**Post date:** [June 3, 2021, 11:19am UTC](https://forum.inductiveautomation.com/t/notification-bug-or-something-else/47389/1 "2021-06-03T11:19:29Z")

</div>

Hello, I have a I/O MOXA device connect to Ignition (V 8.0.15). I have created 3 tags:  
-OPC Tag “Is connected” (goes false when the device is disconnected)  
-Expression Tag “low temperature” (goes true when analog input goes below a threshold)  
-Expression Tag “MOXA Alarm” (goes true when !{[.]Is Connected} || {[.]low temperature}) with configured Notification alarm.

Now, if “MOXA Alarm” change state for “low temperature” start the notification but if change state for “Is connected” doesn’t start.

I tried to remove {[.]low temperature} from “MOXA Alarm” and works but with total expression !{[.]Is Connected} || {[.]low temperature} doesn’t work.

How is it possible?