# \[RESOLVED\] "An alarm could not be acknowledged. It may no longer be registered."

**URL:** <https://forum.inductiveautomation.com/t/resolved-an-alarm-could-not-be-acknowledged-it-may-no-longer-be-registered/108459>\
**Category:** Ignition\
**Created:** [July 15, 2025, 6:12am UTC](https://forum.inductiveautomation.com/t/resolved-an-alarm-could-not-be-acknowledged-it-may-no-longer-be-registered/108459 "2025-07-15T06:12:16Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Craig\_Rathbone](https://avatars.discourse-cdn.com/v4/letter/c/3ec8ea/32.png) [@Craig\_Rathbone](https://forum.inductiveautomation.com/u/Craig_Rathbone)\
**Post date:** [July 15, 2025, 6:12am UTC](https://forum.inductiveautomation.com/t/resolved-an-alarm-could-not-be-acknowledged-it-may-no-longer-be-registered/108459/1 "2025-07-15T06:12:16Z")

</div>

Hi, we had an edge system crash and on restoration we some alarm on the master system that are no longer on the edge but we can't clear them from the alarm page (or by script) and we get a  
"An alarm could not be acknowledged. It may no longer be registered. Event details: 83efbca8-1430-43b0-8bf9-3281156d6b4c / {{ackUser=usr:REDACTED, eventTime=Tue Jul 15 13:53:08 SGT 2025, ackUserName=REDACTED}}"

Have checked on the edge and the alarm is in the events but cleared and acknowledged, have reset the Alarm journal on Edge just in case.

Have set off new instances of said alarms and they come up as new alarms (and clear/acknowledge ok) so I 'm a bit stuck as to how to fix. Anyone else had this happen?

---

<div class="post-metadata">

**Author:** ![Craig\_Rathbone](https://avatars.discourse-cdn.com/v4/letter/c/3ec8ea/32.png) [@Craig\_Rathbone](https://forum.inductiveautomation.com/u/Craig_Rathbone)\
**Post date:** [July 15, 2025, 6:32am UTC](https://forum.inductiveautomation.com/t/resolved-an-alarm-could-not-be-acknowledged-it-may-no-longer-be-registered/108459/2 "2025-07-15T06:32:34Z")

</div>

Resolved.

For those who end up here with the same issue, disable, save then re-enable alarming in the tag provider and they clear out.

---

<div class="post-metadata">

**Author:** ![jesse.daniels](https://avatars.discourse-cdn.com/v4/letter/j/e36b37/32.png) [@jesse.daniels](https://forum.inductiveautomation.com/u/jesse.daniels)\
**Post date:** [August 6, 2026, 6:18pm UTC](https://forum.inductiveautomation.com/t/resolved-an-alarm-could-not-be-acknowledged-it-may-no-longer-be-registered/108459/3 "2026-08-06T18:18:26Z")

</div>

@Craig_Rathbone what are you disabling? alarming on the individual tags? or can i do this to a whole tag provider? from the log, there is an eventid, but nothing for that eventid in the alarm\_events table to look up what tag is causing the issue.

---

<div class="post-metadata">

**Author:** ![Craig\_Rathbone](https://avatars.discourse-cdn.com/v4/letter/c/3ec8ea/32.png) [@Craig\_Rathbone](https://forum.inductiveautomation.com/u/Craig_Rathbone)\
**Post date:** [August 7, 2026, 2:46am UTC](https://forum.inductiveautomation.com/t/resolved-an-alarm-could-not-be-acknowledged-it-may-no-longer-be-registered/108459/4 "2026-08-07T02:46:11Z")

</div>

This was disabling the re-enabling alarmong on the tag provider itself.

---

<div class="post-metadata">

**Author:** ![Transistor](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/transistor/32/3380_2.png) [@Transistor](https://forum.inductiveautomation.com/u/Transistor)\
**Post date:** [August 7, 2026, 7:38am UTC](https://forum.inductiveautomation.com/t/resolved-an-alarm-could-not-be-acknowledged-it-may-no-longer-be-registered/108459/5 "2026-08-07T07:38:22Z")

</div>

Tip: don't put [SOLVED] or [RESOLVED] in your question title. Use the **Solution** button below the post that answers your question - even if you wrote it. You'll see a green checkmark icon on the main page beside each question with an accepted solution.