# Missing Alarms in Alarm Status Table **URL:** \ **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:** 4\ **Page:** 1
**Author:** ![arun1](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/arun1/32/79753_2.png) [@arun1](https://forum.inductiveautomation.com/u/arun1)\ **Post date:** [September 26, 2025, 9:39pm UTC](https://forum.inductiveautomation.com/t/missing-alarms-in-alarm-status-table/111026/1 "2025-09-26T21:39:13Z")
We have a recently installed Ignition Perspective SCADA system. The alarming has been working fine. Few days ago 3 alarms got triggered in the field but did not show up in the Alarm Status table. I went looking in the Alarm Journal and only found their Clear events, and a few months old Active event. So essentially the alarm came in but did not get registered but the clear event was registered. Anyone seen something like this before or any ideas what could be causing this? So far its just these three alarms. Gateway logs are clear around that time the alarm happened. It is a typical Boolean tag (inside a UDT), no fancy scripting or binding: ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/e/2/e209c7d07d02373b22c27aec8bcd49e7017aea94.png) Alarm config is enabled, no active delay, and no pipelines. ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/0/9/09a8588cc85baa3bb8997eb9ce22b11ee0a6ad67.png) Alarm Status and Journal have no filters. I can only find the Clear event and not the Active event for these 3 alarms: ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/7/4/74523fe680e4a1a902f15b2a84e1b60709d435da.png) And the last Active and Ack events were when we were testing the system: ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/6/1/6136740ad49270a446192b1e2ce325da19f3fa13.png) Querying the alarm database with the eventId gives the same result: ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/5/f/5f28b1467b96d17f9fd797bbcd95828cabaa5130.png) A legacy SCADA was also monitoring the same system and it record the field alarm at about 8:56 am on 9/23 ---
**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:** [October 30, 2025, 12:51pm UTC](https://forum.inductiveautomation.com/t/missing-alarms-in-alarm-status-table/111026/2 "2025-10-30T12:51:52Z")
What version of Ignition? I’ve got a server running 8.1.45 that I’m having a similar issue. I watched an alarm pop into the Alarm Status table last night for a split second. And it’s not in the journal at all. ---
**Author:** ![Jill\_Minor](https://avatars.discourse-cdn.com/v4/letter/j/e95f7d/32.png) [@Jill\_Minor](https://forum.inductiveautomation.com/u/Jill_Minor)\ **Post date:** [June 29, 2026, 7:30pm UTC](https://forum.inductiveautomation.com/t/missing-alarms-in-alarm-status-table/111026/3 "2026-06-29T19:30:37Z")
I'm running v8.3.2 and am having issues with alarms designated medium priority showing up in the alarm status table while they are active. Once they clear they show up. The active medium priority alarms will display in the alarm journal and they are present in the gateway. I've remade the table just in case there is a hidden configuration somewhere and it's behaving the same way. I don't feel like I should have to change the priority to high to make sure it displays on the status table. Low priority displays also. ---
**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")
> [@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..