# Performance issue in Ignition when using isAlarmActive() in a Visible expression

**URL:** <https://forum.inductiveautomation.com/t/performance-issue-in-ignition-when-using-isalarmactive-in-a-visible-expression/71221>\
**Category:** Ignition\
**Tags:** ignition81\
**Created:** [March 17, 2023, 10:51am UTC](https://forum.inductiveautomation.com/t/performance-issue-in-ignition-when-using-isalarmactive-in-a-visible-expression/71221 "2023-03-17T10:51:10Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Miguel\_Cimildoro](https://avatars.discourse-cdn.com/v4/letter/m/53a042/32.png) [@Miguel\_Cimildoro](https://forum.inductiveautomation.com/u/Miguel_Cimildoro)\
**Post date:** [March 17, 2023, 10:51am UTC](https://forum.inductiveautomation.com/t/performance-issue-in-ignition-when-using-isalarmactive-in-a-visible-expression/71221/1 "2023-03-17T10:51:10Z")

</div>

I want to open a post in Ignition to discuss the unusual behavior I've noticed when using isAlarmActive() in a Visible expression, which surprisingly increases system performance. I would like to know if anyone else has experienced something similar and get suggestions to solve this problem. Let's work together to understand and improve the performance of our Ignition projects.

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/1/5/151a8e6f8184b054e8021895453e6116148084ee.png)

When I use this method, the system becomes very slow, to the point where I have to use "Control+Alt+Delete" to end the Ignition process and continue with my work.

---

<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:** [March 17, 2023, 12:02pm UTC](https://forum.inductiveautomation.com/t/performance-issue-in-ignition-when-using-isalarmactive-in-a-visible-expression/71221/2 "2023-03-17T12:02:42Z")

</div>

Looks like Vision, I would tag this topic as such. You should also include your version. I haven't used that function, but if it's anything like `system.alarm.queryStatus` it can get quite expensive especially when you have a bunch of instances. I highly recommend that you contact support and open a support ticket so they can guide you through the troubleshooting steps.

You may also look at my exchange resource that helps solve this problem.

> **[Ignition Exchange](https://inductiveautomation.com/exchange/2392/overview)**
>
> Discover, share, and download community made Ignition resources in collaboration with your organization or the Ignition community.