# Medium priority alarms un-filterable in status table and queryStatus

**URL:** <https://forum.inductiveautomation.com/t/medium-priority-alarms-un-filterable-in-status-table-and-querystatus/112185>\
**Category:** Ignition\
**Tags:** ignition83\
**Created:** [November 14, 2025, 3:32pm UTC](https://forum.inductiveautomation.com/t/medium-priority-alarms-un-filterable-in-status-table-and-querystatus/112185 "2025-11-14T15:32:29Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![cmgriggs93](https://avatars.discourse-cdn.com/v4/letter/c/5f8ce5/32.png) [@cmgriggs93](https://forum.inductiveautomation.com/u/cmgriggs93)\
**Post date:** [November 14, 2025, 3:32pm UTC](https://forum.inductiveautomation.com/t/medium-priority-alarms-un-filterable-in-status-table-and-querystatus/112185/1 "2025-11-14T15:32:29Z")

</div>

Running 8.3.1, I found I am not able to retrieve ActiveAcked alarms of Medium priority in the alarm status table. ActiveUnacked alarms are picked up, but will disappear as soon as a user acknowledges them. The behavior is the same in both the alarm status table and via the queryStatus method.

Edit: I tested the same via another gateway (8.1.48) connected as a GNC, using this provider as a remote tag provider. The alarms are appearing in that gateway correctly.

Example. The acked medium alarm is present in one query, but not the filtered query:

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/4/6/46bfcad36e1fd1048829ae21f767fa7a8a2f3620.png)

Alarm status for the tag above, according to the tag browser:

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/a/9/a94ef48028a8f5a29493aee68b6f88d195609112.png)