# Alarm acknowledgment failed - It may no longer be registered

**URL:** <https://forum.inductiveautomation.com/t/alarm-acknowledgment-failed-it-may-no-longer-be-registered/63429>\
**Category:** Ignition\
**Created:** [August 25, 2022, 3:09am UTC](https://forum.inductiveautomation.com/t/alarm-acknowledgment-failed-it-may-no-longer-be-registered/63429 "2022-08-25T03:09:03Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![nminchin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nminchin/32/6911_2.png) [@nminchin](https://forum.inductiveautomation.com/u/nminchin)\
**Post date:** [August 25, 2022, 3:09am UTC](https://forum.inductiveautomation.com/t/alarm-acknowledgment-failed-it-may-no-longer-be-registered/63429/1 "2022-08-25T03:09:03Z")

</div>

A client is getting these errors when trying to acknowledge any alarms.  
 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/3/e/3e98b36a11af51f790cc30b6652df2d7d34dbd1d.png)

This is what the wrapper log reports:

```auto
An alarm could not be acknowledged. It may no longer be registered. Event details: 826ab271-10a9-4968-a09e-3c06a78b404d / {{ackUser=usr-prov:AdminsDB:/usr:nickm, eventTime=Thu Aug 25 11:50:20 ACST 2022}}

```

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/d/2/d299f2ae9c7387e84c658cb7a87e648be661c55a.png)

(@witman, looks like a log msg coming from you! 😄)

Any ideas?

---

<div class="post-metadata">

**Author:** ![witman](https://avatars.discourse-cdn.com/v4/letter/w/d2c977/32.png) [@witman](https://forum.inductiveautomation.com/u/witman)\
**Post date:** [August 25, 2022, 3:19am UTC](https://forum.inductiveautomation.com/t/alarm-acknowledgment-failed-it-may-no-longer-be-registered/63429/2 "2022-08-25T03:19:58Z")

</div>

😄 Saw this earlier today. Might be related 🧐

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/4/1/418b8f98f71b3196cbeba502b8b3c57753744acb.png)

> **[Ignition Release Notes for Version 8.1.20 | Inductive Automation](https://inductiveautomation.com/downloads/releasenotes/8.1.20)**
>
> Fixes, changes and features in Ignition 8.1.20

---

<div class="post-metadata">

**Author:** ![deon.korb](https://avatars.discourse-cdn.com/v4/letter/d/8c91f0/32.png) [@deon.korb](https://forum.inductiveautomation.com/u/deon.korb)\
**Post date:** [September 1, 2022, 10:02am UTC](https://forum.inductiveautomation.com/t/alarm-acknowledgment-failed-it-may-no-longer-be-registered/63429/3 "2022-09-01T10:02:17Z")

</div>

This is still present after upgrading to 8.1.20. Has anyone figured out what causes this?

---

<div class="post-metadata">

**Author:** ![MMaynard](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/mmaynard/32/3366_2.png) [@MMaynard](https://forum.inductiveautomation.com/u/MMaynard)\
**Post date:** [September 2, 2022, 12:02pm UTC](https://forum.inductiveautomation.com/t/alarm-acknowledgment-failed-it-may-no-longer-be-registered/63429/4 "2022-09-02T12:02:37Z")

</div>

We are seeing the same thing. Any resolutions?  
We already moved the ack code to an asynchronous thread.

---

<div class="post-metadata">

**Author:** ![MMaynard](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/mmaynard/32/3366_2.png) [@MMaynard](https://forum.inductiveautomation.com/u/MMaynard)\
**Post date:** [October 14, 2022, 11:34am UTC](https://forum.inductiveautomation.com/t/alarm-acknowledgment-failed-it-may-no-longer-be-registered/63429/5 "2022-10-14T11:34:28Z")

</div>

BUMPING for some insights?

---

<div class="post-metadata">

**Author:** ![MMaynard](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/mmaynard/32/3366_2.png) [@MMaynard](https://forum.inductiveautomation.com/u/MMaynard)\
**Post date:** [April 10, 2023, 8:24pm UTC](https://forum.inductiveautomation.com/t/alarm-acknowledgment-failed-it-may-no-longer-be-registered/63429/6 "2023-04-10T20:24:54Z")

</div>

I _think_ I might have stumbled across a cause of this.  
@paul-griffith could you see if a client workstation having a time that is in the future compared to the gateway would cause this? We use scripting to ack alarms in the selected area, and I just saw this happening live so I could look into a bit.  
I noticed the time in the log for the entries were in the future by two minutes compared to the gateway, went and checked the machine causing the errors and the time was in fact two minutes into the future.

If this is the case, my question would then be why would the local client time be used in place of the gateway time when acknowledging alarms?

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [April 11, 2023, 3:51pm UTC](https://forum.inductiveautomation.com/t/alarm-acknowledgment-failed-it-may-no-longer-be-registered/63429/7 "2023-04-11T15:51:50Z")

</div>

I don't think anything about the timestamp would lead to this, but alarming isn't my area of expertise. That message goes into the logs when the set of IDs to acknowledge goes out, and not all of the UUIDs in the set are removed. Timestamps aren't relevant, as far as I know; the logged message is indicating there's a state mismatch (either you're trying to acknowledge something that no longer exists, or you're trying to ack something that never existed).

I _would_ encourage you and anyone else in this thread with this issue to contact support officially, though.

---

<div class="post-metadata">

**Author:** ![dhiraj.pawar](https://avatars.discourse-cdn.com/v4/letter/d/3ec8ea/32.png) [@dhiraj.pawar](https://forum.inductiveautomation.com/u/dhiraj.pawar)\
**Post date:** [August 16, 2023, 4:57am UTC](https://forum.inductiveautomation.com/t/alarm-acknowledgment-failed-it-may-no-longer-be-registered/63429/8 "2023-08-16T04:57:19Z")

</div>

Hello Team,  
I have same issue with 8.1.28 version. Let me know if any resolution?

---

<div class="post-metadata">

**Author:** ![SBL\_MC](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/sbl_mc/32/56813_2.png) [@SBL\_MC](https://forum.inductiveautomation.com/u/SBL_MC)\
**Post date:** [April 10, 2024, 1:09pm UTC](https://forum.inductiveautomation.com/t/alarm-acknowledgment-failed-it-may-no-longer-be-registered/63429/9 "2024-04-10T13:09:07Z")

</div>

Still present in 8.1.38

---

<div class="post-metadata">

**Author:** ![Stef\_Van\_Poucke](https://avatars.discourse-cdn.com/v4/letter/s/dec6dc/32.png) [@Stef\_Van\_Poucke](https://forum.inductiveautomation.com/u/Stef_Van_Poucke)\
**Post date:** [May 2, 2024, 1:44pm UTC](https://forum.inductiveautomation.com/t/alarm-acknowledgment-failed-it-may-no-longer-be-registered/63429/10 "2024-05-02T13:44:14Z")

</div>

Same issue today with 8.1.38

---

<div class="post-metadata">

**Author:** ![Travis\_Leanna](https://avatars.discourse-cdn.com/v4/letter/t/dec6dc/32.png) [@Travis\_Leanna](https://forum.inductiveautomation.com/u/Travis_Leanna)\
**Post date:** [May 22, 2024, 12:30pm UTC](https://forum.inductiveautomation.com/t/alarm-acknowledgment-failed-it-may-no-longer-be-registered/63429/11 "2024-05-22T12:30:56Z")

</div>

I have also seen this message on a standard alarm acknowledgement, even when trying to acknowledge one alarm at a time. However, we do have the same alarm table running on two different projects and clients. I'm wondering if there's an intermittent conflict between the timing of the two? 8.1.38.

---

<div class="post-metadata">

**Author:** ![Travis\_Leanna](https://avatars.discourse-cdn.com/v4/letter/t/dec6dc/32.png) [@Travis\_Leanna](https://forum.inductiveautomation.com/u/Travis_Leanna)\
**Post date:** [May 22, 2024, 1:19pm UTC](https://forum.inductiveautomation.com/t/alarm-acknowledgment-failed-it-may-no-longer-be-registered/63429/12 "2024-05-22T13:19:55Z")

</div>

I don't know if this information is useful:

Tag was in alarm state from 7:08 to 8:48.  
It was acknowledged at 7:12  
The gateway log has the error at 7:25.

---

<div class="post-metadata">

**Author:** ![ltoscano](https://avatars.discourse-cdn.com/v4/letter/l/3be4f8/32.png) [@ltoscano](https://forum.inductiveautomation.com/u/ltoscano)\
**Post date:** [June 12, 2024, 6:16pm UTC](https://forum.inductiveautomation.com/t/alarm-acknowledgment-failed-it-may-no-longer-be-registered/63429/13 "2024-06-12T18:16:35Z")

</div>

Having the same issues. Running 8.1.37. Anyone come up with anything?

---

<div class="post-metadata">

**Author:** ![mahsasalimi](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/mahsasalimi/32/68520_2.png) [@mahsasalimi](https://forum.inductiveautomation.com/u/mahsasalimi)\
**Post date:** [August 27, 2024, 7:53am UTC](https://forum.inductiveautomation.com/t/alarm-acknowledgment-failed-it-may-no-longer-be-registered/63429/14 "2024-08-27T07:53:05Z")

</div>

I have the same issue .  
Version: 8.1.40

---

<div class="post-metadata">

**Author:** ![Watermark\_JS](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/watermark_js/32/32342_2.png) [@Watermark\_JS](https://forum.inductiveautomation.com/u/Watermark_JS)\
**Post date:** [August 28, 2024, 4:21am UTC](https://forum.inductiveautomation.com/t/alarm-acknowledgment-failed-it-may-no-longer-be-registered/63429/15 "2024-08-28T04:21:13Z")

</div>

Having the same issue in 8.1.41.

---

<div class="post-metadata">

**Author:** ![r123](https://avatars.discourse-cdn.com/v4/letter/r/838e76/32.png) [@r123](https://forum.inductiveautomation.com/u/r123)\
**Post date:** [November 6, 2024, 4:39pm UTC](https://forum.inductiveautomation.com/t/alarm-acknowledgment-failed-it-may-no-longer-be-registered/63429/16 "2024-11-06T16:39:23Z")

</div>

Having the same issue in version: 8.1.44

---

<div class="post-metadata">

**Author:** ![Andreas\_Wallevik](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/andreas_wallevik/32/64045_2.png) [@Andreas\_Wallevik](https://forum.inductiveautomation.com/u/Andreas_Wallevik)\
**Post date:** [January 13, 2025, 8:07am UTC](https://forum.inductiveautomation.com/t/alarm-acknowledgment-failed-it-may-no-longer-be-registered/63429/17 "2025-01-13T08:07:13Z")

</div>

Also getting this error. Has there been a fix / solution to this that anyone know of? Anyone know what causes it?

---

<div class="post-metadata">

**Author:** ![fernando](https://avatars.discourse-cdn.com/v4/letter/f/779978/32.png) [@fernando](https://forum.inductiveautomation.com/u/fernando)\
**Post date:** [June 6, 2025, 6:16pm UTC](https://forum.inductiveautomation.com/t/alarm-acknowledgment-failed-it-may-no-longer-be-registered/63429/18 "2025-06-06T18:16:10Z")

</div>

Maybe you are trying to acknowledge alarms that are alrigth acknowledged.  
I had the same messages and found that my code was not filtering acknowledged alarms.  
This is my code now, with this code I had no more alarm.Manager Warning Messages.

```python
defaultProv = str(system.tag.getConfiguration()[0]['path']).lstrip('[').rstrip(']')

alarmPaths = ['*alarmPath1*', '*alarmPath2*]

stringlist = []

alarms = system.alarm.queryStatus(state=[0,2], path = alarmPaths, provider=[defaultProv])

for id in alarms:
	stringlist.append(str(id.getId()))

try:
	system.alarm.acknowledge(stringlist, None)
except:
	pass

```

---

<div class="post-metadata">

**Author:** ![Cody\_Doyle](https://avatars.discourse-cdn.com/v4/letter/c/8797f3/32.png) [@Cody\_Doyle](https://forum.inductiveautomation.com/u/Cody_Doyle)\
**Post date:** [July 25, 2025, 3:52pm UTC](https://forum.inductiveautomation.com/t/alarm-acknowledgment-failed-it-may-no-longer-be-registered/63429/19 "2025-07-25T15:52:05Z")

</div>

As an extension of Fernando's note, there is a known bug with the Alarm Status Table in Perspective where acknowledging previously acknowledged alarms result in the alarm.Manager Warning messages we see here (IGN-9948).

So if you are not scripting your acknowledgements, you may be running into that bug instead.

---

<div class="post-metadata">

**Author:** ![jeremy.anderson](https://avatars.discourse-cdn.com/v4/letter/j/e36b37/32.png) [@jeremy.anderson](https://forum.inductiveautomation.com/u/jeremy.anderson)\
**Post date:** [April 2, 2026, 3:15pm UTC](https://forum.inductiveautomation.com/t/alarm-acknowledgment-failed-it-may-no-longer-be-registered/63429/20 "2026-04-02T15:15:57Z")

</div>

We are seeing this bug in 8.1.49. It occurs for us while trying to acknowledge alarms in the Alarm Status Table in Vision.