# \[BUG\] 8.1.0 Perspective alarm status display filter (expression-bound) only sometimes works **URL:** \ **Category:** Ignition\ **Tags:** ignition80, perspective\ **Created:** [November 19, 2020, 1:49am UTC](https://forum.inductiveautomation.com/t/bug-8-1-0-perspective-alarm-status-display-filter-expression-bound-only-sometimes-works/40785 "2020-11-19T01:49:39Z")\ **Posts on this page:** 1\ **Showing post:** 13
**Author:** ![justin.brzozoski](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/justin.brzozoski/32/13452_2.png) [@justin.brzozoski](https://forum.inductiveautomation.com/u/justin.brzozoski)\ **Post date:** [March 3, 2021, 6:15pm UTC](https://forum.inductiveautomation.com/t/bug-8-1-0-perspective-alarm-status-display-filter-expression-bound-only-sometimes-works/40785/13 "2021-03-03T18:15:31Z")
Can confirm we've seen this happen maybe 4 times in the past month on our 8.1.0 instance as well. We have not been able to reproduce the issue intentionally yet. As Nick said, when a browser lands on the view without a filter, it never self-corrects. The user has to hit refresh on the browser to fix it. Some extra info about our setup: along with the binding on `props.filters.active.conditions.source`, we also have the `Persistent` property enabled and a default value that should point to no alarms (`prov:MQTT Engine:/tag:Edge Nodes/invalid/none/*`). Somehow it looks like both the persistent setting and the binding are ignored when it breaks. Is there any chance this was improved/fixed in a later 8.1.x release? Knowing so would increase the priority of our upgrade plans. (We plan on upgrading, but other issues are more important right now.) Related thread: > [@Perspective Alarm Status Filtering](http://forum.inductiveautomation.com/t/perspective-alarm-status-filtering/41069): > > We have the alarm status on popups for the different devices. The alarm status table is in a tab strip container, as an embedded view. One of the params that is passed to the alarm view is the tag to filter on in the table. We are using the filters.active.conditions.source to filter the alarms. What is happening is when the tab containing the alarm view is clicked, all the active alarms are shown, and then the filter is applied. Is this supposed to be happening that way? Any way we can get it t… --- _[View the full topic](https://forum.inductiveautomation.com/t/bug-8-1-0-perspective-alarm-status-display-filter-expression-bound-only-sometimes-works/40785)._