# Filters not immediately applied to Alarm Status Table

**URL:** <https://forum.inductiveautomation.com/t/filters-not-immediately-applied-to-alarm-status-table/66072>\
**Category:** Ignition\
**Tags:** perspective\
**Created:** [November 3, 2022, 2:09pm UTC](https://forum.inductiveautomation.com/t/filters-not-immediately-applied-to-alarm-status-table/66072 "2022-11-03T14:09:56Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![manuele.longhi](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/manuele.longhi/32/51470_2.png) [@manuele.longhi](https://forum.inductiveautomation.com/u/manuele.longhi)\
**Post date:** [November 3, 2022, 2:09pm UTC](https://forum.inductiveautomation.com/t/filters-not-immediately-applied-to-alarm-status-table/66072/1 "2022-11-03T14:09:56Z")

</div>

I have defined a bunch of alarms, each with a display path with the structure

\<plant\>/\<area\>/[...]/\<work cell\>

_ **Examples** :  
PlantName1/Finishing/Dispencer  
PlantName2/Foundry/Melting/Furnace_

After that, I have defined a Perspective page that takes in input the name of the plant as well as (_optionally_) the name of a work cell. In the page I have an AlarmStatusTable component, that has a display path filter (defined on "props.filters.active.conditions.displayPath") defined as follows:

- if no work cell is not specified, the filter is "\<plant\>/\*"
- if a work cell is specified, the filter becomes "\<plant\>/\*/\<work cell\>"

_ **Examples** :  
PlantName1/\*  
PlantName2/\*/Furnace_

This allows me to only show the alarms that are currently active for the plant that I choose.  
However, for a few seconds when I load the page, it seems like the filter is not applied and I am able to see every alarm currently active, regardless of the plant I specified.  
After a few seconds (~ 5-10 seconds) the filter is applied and everything works smoothly.

Is there a way to avoid this behaviour?

Thanks

---

<div class="post-metadata">

**Author:** ![Jacob\_Klever](https://avatars.discourse-cdn.com/v4/letter/j/ee7513/32.png) [@Jacob\_Klever](https://forum.inductiveautomation.com/u/Jacob_Klever)\
**Post date:** [November 10, 2022, 10:46pm UTC](https://forum.inductiveautomation.com/t/filters-not-immediately-applied-to-alarm-status-table/66072/2 "2022-11-10T22:46:40Z")

</div>

Hello Manuele,

How many active alarms to display are you pulling into this alarm status table? I am wondering if the alarm status table simply takes that 5-10 seconds to load in those alarms before applying the filter.

---

<div class="post-metadata">

**Author:** ![Jacob\_Klever](https://avatars.discourse-cdn.com/v4/letter/j/ee7513/32.png) [@Jacob\_Klever](https://forum.inductiveautomation.com/u/Jacob_Klever)\
**Post date:** [November 10, 2022, 11:52pm UTC](https://forum.inductiveautomation.com/t/filters-not-immediately-applied-to-alarm-status-table/66072/3 "2022-11-10T23:52:32Z")

</div>

It look like this is a know bug. Upgrading to 8.1.19 should resolve the issue. Alarm tables no longer discard incoming changes to filters when actively performing a polling query.

> **[Ignition Release Notes for Version 8.1.19 | Inductive Automation](https://inductiveautomation.com/downloads/releasenotes/8.1.19)**
>
> Fixes, changes and features in Ignition 8.1.19