# Alarm Journal vs Alarm Status Table **URL:** \ **Category:** Ignition\ **Created:** [February 29, 2024, 5:20pm UTC](https://forum.inductiveautomation.com/t/alarm-journal-vs-alarm-status-table/86618 "2024-02-29T17:20:29Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![melwadeya](https://avatars.discourse-cdn.com/v4/letter/m/ed8c4c/32.png) [@melwadeya](https://forum.inductiveautomation.com/u/melwadeya)\ **Post date:** [February 29, 2024, 5:20pm UTC](https://forum.inductiveautomation.com/t/alarm-journal-vs-alarm-status-table/86618/1 "2024-02-29T17:20:29Z")
Hi In Ignition version 8.1.20, two alarms associated with a single tag went active and were then acknowledged. However, the event of these alarms transitioning to the active state and being acknowledged is not appearing in the alarm journal. The alarms have not been cleared, only acknowledged. It's been about two hours and still nothing in the alarm journal. what could be the reason? note: this has not happened before and alarm journal has lots of events in it. ---
**Author:** ![drojas](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/drojas/32/3403_2.png) [@drojas](https://forum.inductiveautomation.com/u/drojas)\ **Post date:** [February 29, 2024, 6:35pm UTC](https://forum.inductiveautomation.com/t/alarm-journal-vs-alarm-status-table/86618/2 "2024-02-29T18:35:43Z")
The alarm journal relies on the SQL table alarm\_events and alarm\_event\_data. Perhaps something happened to the connection where it is no longer saving data there. The alarm status pulls from Ignition's internal alarm state. ---
**Author:** ![melwadeya](https://avatars.discourse-cdn.com/v4/letter/m/ed8c4c/32.png) [@melwadeya](https://forum.inductiveautomation.com/u/melwadeya)\ **Post date:** [February 29, 2024, 7:50pm UTC](https://forum.inductiveautomation.com/t/alarm-journal-vs-alarm-status-table/86618/3 "2024-02-29T19:50:47Z")
The SQL table does not display the alarm event. Although the alarm journal shows events before and after, it skipped the two alarm events, which are still active but not indicated as active or acknowledged ---
**Author:** ![melwadeya](https://avatars.discourse-cdn.com/v4/letter/m/ed8c4c/32.png) [@melwadeya](https://forum.inductiveautomation.com/u/melwadeya)\ **Post date:** [February 29, 2024, 7:54pm UTC](https://forum.inductiveautomation.com/t/alarm-journal-vs-alarm-status-table/86618/4 "2024-02-29T19:54:50Z")
![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/4/4/4436115bc23bfa576a5c5a66e2365c3470efd1d2.jpeg) ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/3/6/361a5cc7c7b0bd5840803efff38a02fd7350bec5.png) ---
**Author:** ![drojas](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/drojas/32/3403_2.png) [@drojas](https://forum.inductiveautomation.com/u/drojas)\ **Post date:** [February 29, 2024, 8:16pm UTC](https://forum.inductiveautomation.com/t/alarm-journal-vs-alarm-status-table/86618/5 "2024-02-29T20:16:43Z")
Can you double check if you have any Data Filters applied that prevented that tag from being recorded. I can see the last time an event for that specific tag was back on the 23rd. The eventflags is 0 which indicates it is the entry for when it became Active. Also, another possibility is that the gateway has recently restarted and the "Active Time" column will show the time of the gateway System Startup (or a few minutes after). This may be the reason why the 29 Feb 2024 10:07:57 is not found and will not match the eventtime of 2024-02-23 14:29:47. Try removing the "WHERE" clause in your query and see if you have any System Startup events. However, this doesn't explain the lack of Acknowledged event...so I would still look at the health of the database connection. ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/a/4/a41c8b11dd526ab6164b2cd44f6c38dceab45110.png) ---
**Author:** ![drojas](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/drojas/32/3403_2.png) [@drojas](https://forum.inductiveautomation.com/u/drojas)\ **Post date:** [February 29, 2024, 8:55pm UTC](https://forum.inductiveautomation.com/t/alarm-journal-vs-alarm-status-table/86618/6 "2024-02-29T20:55:43Z")
Also, looks like this might be a known issue that was resolved in version .36. > **[Ignition Release Notes for Version 8.1.36 | Inductive Automation](https://inductiveautomation.com/downloads/releasenotes/8.1.36)** > > Fixes, changes and features in Ignition 8.1.36 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/4/8/4864b2e9eef9e41562021921df1975d9296cc13b.png) ---
**Author:** ![jlandwerlen](https://avatars.discourse-cdn.com/v4/letter/j/bc8723/32.png) [@jlandwerlen](https://forum.inductiveautomation.com/u/jlandwerlen)\ **Post date:** [March 1, 2024, 12:03pm UTC](https://forum.inductiveautomation.com/t/alarm-journal-vs-alarm-status-table/86618/7 "2024-03-01T12:03:01Z")
What is the priority of the alarm? Perhaps the priority is lower than the min setting in the alarm journal setting in the gateway webpage. I think by default, diagnostic alarms will not be stored.