# Missing Alarms in Alarm Status Table

**URL:** <https://forum.inductiveautomation.com/t/missing-alarms-in-alarm-status-table/111026>\
**Category:** Ignition\
**Tags:** perspective, ignition81\
**Created:** [September 26, 2025, 9:39pm UTC](https://forum.inductiveautomation.com/t/missing-alarms-in-alarm-status-table/111026 "2025-09-26T21:39:13Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![tgarrison](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/tgarrison/32/80965_2.png) [@tgarrison](https://forum.inductiveautomation.com/u/tgarrison)\
**Post date:** [June 29, 2026, 8:36pm UTC](https://forum.inductiveautomation.com/t/missing-alarms-in-alarm-status-table/111026/4 "2026-06-29T20:36:49Z")

</div>

> [@system.alarm.queryStatus() inconsistent results](https://forum.inductiveautomation.com/t/system-alarm-querystatus-inconsistent-results/115662):
>
> Came across what appears to be a bug in system.tag.queryStatus(). I've got a ticket open with support already, but figured I'd post here so others can know about it. when calling system.tag.queryStatus(status=['ClearUnacked']) I'm getting different results then when I run system.tag.queryStatus(status=['ClearUnacked'], priority=[0,1,2,3,4]). Without declaring all the priorities, I'm missing alarms... Same with the other status. Basically, it appears that not explicitly declaring all the …

See if that gets you anywhere..

---

_[View the full topic](https://forum.inductiveautomation.com/t/missing-alarms-in-alarm-status-table/111026)._