# Alarm Journal Event Flag Definitions

**URL:** <https://forum.inductiveautomation.com/t/alarm-journal-event-flag-definitions/17031>\
**Category:** Ignition\
**Created:** [February 19, 2018, 1:26am UTC](https://forum.inductiveautomation.com/t/alarm-journal-event-flag-definitions/17031 "2018-02-19T01:26:22Z")\
**Posts on this page:** 13\
**Page:** 1

<div class="post-metadata">

**Author:** ![JMicky](https://avatars.discourse-cdn.com/v4/letter/j/dfb087/32.png) [@JMicky](https://forum.inductiveautomation.com/u/JMicky)\
**Post date:** [February 19, 2018, 1:26am UTC](https://forum.inductiveautomation.com/t/alarm-journal-event-flag-definitions/17031/1 "2018-02-19T01:26:22Z")

</div>

Hi,

Is there a full description of all possible eventflags in the alarm journal eventflags table?  
The manual shows definitions for bits 0, 1 and 2 in [https://docs.inductiveautomation.com/display/DOC79/Journal+Properties+and+Tables](https://docs.inductiveautomation.com/display/DOC79/Journal+Properties+and+Tables)

I’m seeing eventflags of 28 in my alarm journal alarm\_events table. This would be bits 2, 3 and 4.  
It looks like these are generated on a gateway startup. Looks like all configured alarms that are not active when the gateway is started are logged to the alarm\_events table with eventflags = 28 and eventtype=1.

 ![](https://us1.discourse-cdn.com/inductiveautomation/original/2X/2/22836ded0011b01c3b5c29a6084406659ee7fcfa.png)

This is in Ignition V7.9.4

Thank you,  
John

---

<div class="post-metadata">

**Author:** ![KathyApplebaum](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kathyapplebaum/32/7261_2.png) [@KathyApplebaum](https://forum.inductiveautomation.com/u/KathyApplebaum)\
**Post date:** [February 20, 2018, 4:24pm UTC](https://forum.inductiveautomation.com/t/alarm-journal-event-flag-definitions/17031/2 "2018-02-20T16:24:36Z")

</div>

Good catch – I’ll get the docs updated.

Bit 3 is IS\_ACKED\_FLAG and bit 4 is IS\_CLEAR\_FLAG. These were added in 7.8.5 to make the Alarm Journal behave more consistently.

---

<div class="post-metadata">

**Author:** ![dhananjay\_vichare](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/dhananjay_vichare/32/74712_2.png) [@dhananjay\_vichare](https://forum.inductiveautomation.com/u/dhananjay_vichare)\
**Post date:** [May 30, 2018, 9:44am UTC](https://forum.inductiveautomation.com/t/alarm-journal-event-flag-definitions/17031/3 "2018-05-30T09:44:12Z")

</div>

Hi Kathy

You mean to say that 7.9.5? We are facing same problem, please confirm.

---

<div class="post-metadata">

**Author:** ![KathyApplebaum](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kathyapplebaum/32/7261_2.png) [@KathyApplebaum](https://forum.inductiveautomation.com/u/KathyApplebaum)\
**Post date:** [May 30, 2018, 2:25pm UTC](https://forum.inductiveautomation.com/t/alarm-journal-event-flag-definitions/17031/4 "2018-05-30T14:25:47Z")

</div>

IS\_ACKED\_FLAG was added in 7.8.5. IS\_CLEAR\_FLAG was added in 7.9.3 or 7.9.4

---

<div class="post-metadata">

**Author:** ![dhananjay\_vichare](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/dhananjay_vichare/32/74712_2.png) [@dhananjay\_vichare](https://forum.inductiveautomation.com/u/dhananjay_vichare)\
**Post date:** [May 31, 2018, 1:28pm UTC](https://forum.inductiveautomation.com/t/alarm-journal-event-flag-definitions/17031/5 "2018-05-31T13:28:40Z")

</div>

Hi Kathy,

We are thinking that this is a bug in 7.9.4 and it was fixed in 7.9.5, hence i have asked that it is 7.8.5 or 7.9.5.  
Is there any solution to fix this issue, as we are getting lot of false alarms on gateway restart and those are not cleared from alarm status table?

Thanks in advance.

---

<div class="post-metadata">

**Author:** ![KathyApplebaum](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kathyapplebaum/32/7261_2.png) [@KathyApplebaum](https://forum.inductiveautomation.com/u/KathyApplebaum)\
**Post date:** [May 31, 2018, 1:32pm UTC](https://forum.inductiveautomation.com/t/alarm-journal-event-flag-definitions/17031/6 "2018-05-31T13:32:20Z")

</div>

Your best bet is to contact support with this.

---

<div class="post-metadata">

**Author:** ![JMicky](https://avatars.discourse-cdn.com/v4/letter/j/dfb087/32.png) [@JMicky](https://forum.inductiveautomation.com/u/JMicky)\
**Post date:** [May 31, 2018, 1:47pm UTC](https://forum.inductiveautomation.com/t/alarm-journal-event-flag-definitions/17031/7 "2018-05-31T13:47:58Z")

</div>

Hi Kathy and Dhananjay,

If possible, can you post the results back to this thread? I am also still interested in the conditions and rules that drive the alarms to be re-triggered at gateway startup for all configured alarms.

Thank you,

John

---

<div class="post-metadata">

**Author:** ![Michal\_Drapal](https://avatars.discourse-cdn.com/v4/letter/m/838e76/32.png) [@Michal\_Drapal](https://forum.inductiveautomation.com/u/Michal_Drapal)\
**Post date:** [March 6, 2023, 10:29am UTC](https://forum.inductiveautomation.com/t/alarm-journal-event-flag-definitions/17031/8 "2023-03-06T10:29:57Z")

</div>

Hello guys,  
could I ask you, do we have some update regarding to this topic? We run into the same issue, when we are having value of 24 for eventflags...  
Thanks,  
Michal

---

<div class="post-metadata">

**Author:** ![justinedwards.jle](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/justinedwards.jle/32/37854_2.png) [@justinedwards.jle](https://forum.inductiveautomation.com/u/justinedwards.jle)\
**Post date:** [March 6, 2023, 10:53am UTC](https://forum.inductiveautomation.com/t/alarm-journal-event-flag-definitions/17031/9 "2023-03-06T10:53:37Z")

</div>

> [@Michal\_Drapal](#):
>
> we are having value of 24 for eventflags...

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/e/9/e9a48e0b4f83f8865b05322c33638d78b24326e5.png)

2 = Automatically Acknowledged  
4 = Cleared

24 = Acknowledged (by the system) and Cleared (alarm condition no longer present)

---

<div class="post-metadata">

**Author:** ![Dimitris\_Katsaros](https://avatars.discourse-cdn.com/v4/letter/d/96bed5/32.png) [@Dimitris\_Katsaros](https://forum.inductiveautomation.com/u/Dimitris_Katsaros)\
**Post date:** [March 6, 2023, 11:24am UTC](https://forum.inductiveautomation.com/t/alarm-journal-event-flag-definitions/17031/10 "2023-03-06T11:24:31Z")

</div>

I have the same problem. The bits go up to 5, but I'm also getting '16' as a value.  
 ![Screenshot_1](https://us1.discourse-cdn.com/inductiveautomation/original/3X/9/8/98e837068ba8489e1d6a8c431c9d123a1b1cb987.png)

---

<div class="post-metadata">

**Author:** ![justinedwards.jle](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/justinedwards.jle/32/37854_2.png) [@justinedwards.jle](https://forum.inductiveautomation.com/u/justinedwards.jle)\
**Post date:** [March 6, 2023, 11:36am UTC](https://forum.inductiveautomation.com/t/alarm-journal-event-flag-definitions/17031/11 "2023-03-06T11:36:56Z")

</div>

> [@Dimitris\_Katsaros](#):
>
> I'm also getting '16'

Interesting. Either the documentation is incomplete, or I've interpreted it wrong.

---

<div class="post-metadata">

**Author:** ![Dimitris\_Katsaros](https://avatars.discourse-cdn.com/v4/letter/d/96bed5/32.png) [@Dimitris\_Katsaros](https://forum.inductiveautomation.com/u/Dimitris_Katsaros)\
**Post date:** [March 6, 2023, 3:37pm UTC](https://forum.inductiveautomation.com/t/alarm-journal-event-flag-definitions/17031/12 "2023-03-06T15:37:17Z")

</div>

I think the answer to that is this

 ![Screenshot_1](https://us1.discourse-cdn.com/inductiveautomation/original/3X/f/b/fbce57bf0caa7167cde862f996bfa0f82f7092ba.png)  
 ![Screenshot_2](https://us1.discourse-cdn.com/inductiveautomation/original/3X/c/9/c97f6e2eccf1efd674c6857efdb28469b04b9eed.png)  
It's basically the binary representation in decimal an from there you get your bits, but I'm not sure. I would love if someone can confirm it

---

<div class="post-metadata">

**Author:** ![JMicky](https://avatars.discourse-cdn.com/v4/letter/j/dfb087/32.png) [@JMicky](https://forum.inductiveautomation.com/u/JMicky)\
**Post date:** [March 6, 2023, 3:37pm UTC](https://forum.inductiveautomation.com/t/alarm-journal-event-flag-definitions/17031/13 "2023-03-06T15:37:31Z")

</div>

The event flags are binary bit positions of the decimal integer.  
Bit 0 has value of 1  
Bit 1 has value of 2  
Bit 2 has value of 4  
Bit 3 has value of 8  
Bit 4 has value of 16

Decimal value of 16 corresponds to binary 10000. Bit 4 is the only bit on, so it is a Cleared Event.  
Decimal value of 24 corresponds to binary 11000. Bits 3 and 4 are on, so it is Acknowledged Event and Cleared Event.
