# Automatic Alarm Acknowledgement in Journal **URL:** \ **Category:** Ignition\ **Tags:** perspective\ **Created:** [July 24, 2025, 1:29am UTC](https://forum.inductiveautomation.com/t/automatic-alarm-acknowledgement-in-journal/108868 "2025-07-24T01:29:55Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![Alex\_Godfrey](https://avatars.discourse-cdn.com/v4/letter/a/e56c9b/32.png) [@Alex\_Godfrey](https://forum.inductiveautomation.com/u/Alex_Godfrey)\ **Post date:** [July 24, 2025, 1:29am UTC](https://forum.inductiveautomation.com/t/automatic-alarm-acknowledgement-in-journal/108868/1 "2025-07-24T01:29:55Z")
Good Morning, I am working on Ignition 8.1. I have set up an alarm on a tag as such: ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/7/3/73de6c265f390ad576104b422a30e0452791308c.png) Within my alarm journal, I am noticing an active and acknowledge state appearing at the same time despite not manually acknowledging the alarm. See screenshot of the alarm journal below. I changed the live event limit from 5 to 10 and I noticed the alarms no longer acknowledging. However, when flushing buffered data to that tag the acknowledging issue persisted. It is my understanding that for a single alarm on a single tag, only one alarm event would be present at any given time, therefore the limit of 5 should not show any difference then a limit of 10 (please let me know if this is incorrect). We have noticed this issue occur in other projects so would love to get to the bottom of this. ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/1/4/14468233f32aad05fe13548e49d1ea1b429e5640.png) Thank you in advance for your help!! ---
**Author:** ![Chris\_Murphy](https://avatars.discourse-cdn.com/v4/letter/c/c5a1d2/32.png) [@Chris\_Murphy](https://forum.inductiveautomation.com/u/Chris_Murphy)\ **Post date:** [July 26, 2025, 1:57am UTC](https://forum.inductiveautomation.com/t/automatic-alarm-acknowledgement-in-journal/108868/2 "2025-07-26T01:57:48Z")
Hi, Maybe try querying the journal directly so you can see the event type and flags associated with that ack record. It looks like it might be a system acknowledgement of the previous cleared unacknowledged alarm.