# False Cleared and Acknowledged Alarm

**URL:** <https://forum.inductiveautomation.com/t/false-cleared-and-acknowledged-alarm/66108>\
**Category:** Ignition\
**Tags:** ignition81, perspective\
**Created:** [November 4, 2022, 12:40am UTC](https://forum.inductiveautomation.com/t/false-cleared-and-acknowledged-alarm/66108 "2022-11-04T00:40:40Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jaron\_Hafso](https://avatars.discourse-cdn.com/v4/letter/j/6de8d8/32.png) [@Jaron\_Hafso](https://forum.inductiveautomation.com/u/Jaron_Hafso)\
**Post date:** [November 4, 2022, 12:40am UTC](https://forum.inductiveautomation.com/t/false-cleared-and-acknowledged-alarm/66108/1 "2022-11-04T00:40:40Z")

</div>

Perspective - Ignition 8.1.18

I’ve noticed the act of creating or modifying certain alarms has caused them to trigger despite never being in alarm condition. After editing an alarm, a cleared and acknowledged state alarm will generate. The alarm was never in an active or unacknowledged state before this.

**Background Information**  
The alarm is based on a derived tag that uses a case structure in the read expression:

> case({source},1,"String1",2,"String2","String3")

The alarm uses the “On Condition” mode with a string comparison in the “Is Active” expression binding:

> {value}="String1"

The alarm operates as expected after the first erroneous alarm is generated.

Is this false alarm expected behavior? Is this a known bug? Do the expression bindings somehow leave room for a momentary true command?

Thanks for any assistance!

---

<div class="post-metadata">

**Author:** ![Jaron\_Hafso](https://avatars.discourse-cdn.com/v4/letter/j/6de8d8/32.png) [@Jaron\_Hafso](https://forum.inductiveautomation.com/u/Jaron_Hafso)\
**Post date:** [November 4, 2022, 5:05pm UTC](https://forum.inductiveautomation.com/t/false-cleared-and-acknowledged-alarm/66108/2 "2022-11-04T17:05:45Z")

</div>

The same alarm behavior has also been witnessed with simple boolean tags; it doesn't look like it's an issue with the expression logic. Root cause is still unknown...

---

<div class="post-metadata">

**Author:** ![jlandwerlen](https://avatars.discourse-cdn.com/v4/letter/j/bc8723/32.png) [@jlandwerlen](https://forum.inductiveautomation.com/u/jlandwerlen)\
**Post date:** [November 5, 2022, 3:19am UTC](https://forum.inductiveautomation.com/t/false-cleared-and-acknowledged-alarm/66108/3 "2022-11-05T03:19:27Z")

</div>

I haven't noticed any issues, especially using simple boolean tags. The default alarm mode setpoint is 0, so if you didn't change to 1 and saved and the tag is low, of course you will see an alarm.

---

<div class="post-metadata">

**Author:** ![edward.fowler](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/edward.fowler/32/24179_2.png) [@edward.fowler](https://forum.inductiveautomation.com/u/edward.fowler)\
**Post date:** [November 5, 2022, 4:20pm UTC](https://forum.inductiveautomation.com/t/false-cleared-and-acknowledged-alarm/66108/4 "2022-11-05T16:20:08Z")

</div>

Here's another post about the same issue.  
@Jaron_Hafso Hi! I think its just an Ignition thing. I don't believe is is actually activating.

> [@Alarm Cleared but Never Active](https://forum.inductiveautomation.com/t/alarm-cleared-but-never-active/62919/5):
>
> I've noticed the same thing. I think its just an Ignition thing. Look at the active and clear times...identical. There weren't new alarms but I did make a change to the UDT where they are configured. Not all changes to the UDT do this, just some, like adding a new member tag. [image]