# system.alarm.queryStatus() inconsistent results

**URL:** <https://forum.inductiveautomation.com/t/system-alarm-querystatus-inconsistent-results/115662>\
**Category:** Ignition\
**Tags:** ignition83\
**Created:** [May 22, 2026, 12:29pm UTC](https://forum.inductiveautomation.com/t/system-alarm-querystatus-inconsistent-results/115662 "2026-05-22T12:29:54Z")\
**Posts on this page:** 1\
**Page:** 1

<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:** [May 22, 2026, 12:29pm UTC](https://forum.inductiveautomation.com/t/system-alarm-querystatus-inconsistent-results/115662/1 "2026-05-22T12:29:54Z")

</div>

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 priorities triggers the bug. I see the same thing in the Alarm Status Table. But unfortunately there, you can't explicitly declare all the priorities as it reverts to show all, which declares none of them.