# Alarm Journal / Acknowledge Issues

**URL:** <https://forum.inductiveautomation.com/t/alarm-journal-acknowledge-issues/104029>\
**Category:** Ignition\
**Tags:** perspective\
**Created:** [March 21, 2025, 7:00pm UTC](https://forum.inductiveautomation.com/t/alarm-journal-acknowledge-issues/104029 "2025-03-21T19:00:51Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![tebright1](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/tebright1/32/87405_2.png) [@tebright1](https://forum.inductiveautomation.com/u/tebright1)\
**Post date:** [March 21, 2025, 7:00pm UTC](https://forum.inductiveautomation.com/t/alarm-journal-acknowledge-issues/104029/1 "2025-03-21T19:00:51Z")

</div>

I have some remote alarm journals setup to share to a Main Gateway. Running into two issues.

1. I cannot Shelve an alarm on the main alarm journal. The edge device (remote) journal can shelve their alarms. How do I allow this to work?  

2. The other issue I am having is, after acknowledging an alarm, it is good until a value change occurs. Which retriggers the alarm. It is becoming a nuisance. I have played with the dead band settings. I want to be able to acknowledge and not look at the alarm again if it is over or under the alarm setpoint. The acknowledged alarm should stay acknowledged.

---

<div class="post-metadata">

**Author:** ![kvane](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kvane/32/22228_2.png) [@kvane](https://forum.inductiveautomation.com/u/kvane)\
**Post date:** [March 21, 2025, 11:10pm UTC](https://forum.inductiveautomation.com/t/alarm-journal-acknowledge-issues/104029/2 "2025-03-21T23:10:02Z")

</div>

Service Security is most likely what you are running into for the 1st point:

> **[Service Security | Ignition User Manual](https://www.docs.inductiveautomation.com/docs/8.1/platform/security/service-security#service-security)**
>
> Service Security

`For this Gateway to shelve alarms on others, this must be set on the remote Gateway.`

For the 2nd point, I am going to state how alarm behavior is expected to function:

- A new live alarm creates an Active, Unacked event
- Once it exists, a live alarm event can be either Cleared and/or Acknowledged
- Once an Alarm is Cleared (no longer active), that live alarm is now completed, and the system will keep it in memory based on a few criteria
- The next alarm event will generate when the alarm triggers

So if a Below Setpoint alarm triggers, and then becomes cleared, then as soon as it triggers again a new active alarm event is generated. If the acknowledgment was on a prior alarm event. The alarm event you acknowledged is still acked, but there is now a new event.

Changing the clear delay is a possible solution.

---

<div class="post-metadata">

**Author:** ![tebright1](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/tebright1/32/87405_2.png) [@tebright1](https://forum.inductiveautomation.com/u/tebright1)\
**Post date:** [March 25, 2025, 12:27pm UTC](https://forum.inductiveautomation.com/t/alarm-journal-acknowledge-issues/104029/3 "2025-03-25T12:27:32Z")

</div>

So for some reason, the Allow Shelving was not checked on my edge device. Must have missed that. 🤦‍♂️

Thanks!