# Alarm could not be acknowledged. It may no longer be registered

**URL:** <https://forum.inductiveautomation.com/t/alarm-could-not-be-acknowledged-it-may-no-longer-be-registered/15685>\
**Category:** Ignition\
**Created:** [October 17, 2017, 3:58am UTC](https://forum.inductiveautomation.com/t/alarm-could-not-be-acknowledged-it-may-no-longer-be-registered/15685 "2017-10-17T03:58:47Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![hgarner](https://avatars.discourse-cdn.com/v4/letter/h/9d8465/32.png) [@hgarner](https://forum.inductiveautomation.com/u/hgarner)\
**Post date:** [October 17, 2017, 3:58am UTC](https://forum.inductiveautomation.com/t/alarm-could-not-be-acknowledged-it-may-no-longer-be-registered/15685/1 "2017-10-17T03:58:47Z")

</div>

We have been experiencing some issues with log messages when we clear out alarms showing the following type entries. If only a few alarms are acknowledged this does not cause any issues, but if there are several alarms this can cause the client to freeze for some time which is troublesome for us as our HMI is not responsive during this time. We are using Ignition v7.9.3.

```auto
INFO | jvm 1 | 2017/10/16 14:00:57 | W [a.Manager] [18:00:57]: An alarm could not be acknowledged. It may no longer be registered. Event details: b7b760c2-9839-43f8-9d73-4ddac33ec9d9 / {{ackUser=usr-prov:default:/usr:level1, eventTime=Mon Oct 16 14:00:57 EDT 2017}} request-origin=127.0.0.1, session-user=level1, session-project=UT3DrawTowerHmi, session-id=32964AC1
INFO | jvm 1 | 2017/10/16 14:00:57 | W [a.Manager] [18:00:57]: An alarm could not be acknowledged. It may no longer be registered. Event details: a6490b29-3073-4592-949d-adde96074996 / {{ackUser=usr-prov:default:/usr:level1, eventTime=Mon Oct 16 14:00:57 EDT 2017}} request-origin=127.0.0.1, session-user=level1, session-project=UT3DrawTowerHmi, session-id=32964AC1
INFO | jvm 1 | 2017/10/16 14:00:57 | W [a.Manager] [18:00:57]: An alarm could not be acknowledged. It may no longer be registered. Event details: a3935c2e-9dd6-4469-9522-16c6a88a7691 / {{ackUser=usr-prov:default:/usr:level1, eventTime=Mon Oct 16 14:00:57 EDT 2017}} request-origin=127.0.0.1, session-user=level1, session-project=UT3DrawTowerHmi, session-id=32964AC1
INFO | jvm 1 | 2017/10/16 14:00:57 | W [a.Manager] [18:00:57]: An alarm could not be acknowledged. It may no longer be registered. Event details: b7b760c2-9839-43f8-9d73-4ddac33ec9d9 / {{ackUser=usr-prov:default:/usr:level1, eventTime=Mon Oct 16 14:00:57 EDT 2017}} request-origin=127.0.0.1, session-user=level1, session-project=UT3DrawTowerHmi, session-id=32964AC1
INFO | jvm 1 | 2017/10/16 14:00:57 | W [a.Manager] [18:00:57]: An alarm could not be acknowledged. It may no longer be registered. Event details: a6490b29-3073-4592-949d-adde96074996 / {{ackUser=usr-prov:default:/usr:level1, eventTime=Mon Oct 16 14:00:57 EDT 2017}} request-origin=127.0.0.1, session-user=level1, session-project=UT3DrawTowerHmi, session-id=32964AC1
INFO | jvm 1 | 2017/10/16 14:00:57 | W [a.Manager] [18:00:57]: An alarm could not be acknowledged. It may no longer be registered. Event details: a3935c2e-9dd6-4469-9522-16c6a88a7691 / {{ackUser=usr-prov:default:/usr:level1, eventTime=Mon Oct 16 14:00:57 EDT 2017}} request-origin=127.0.0.1, session-user=level1, session-project=UT3DrawTowerHmi, session-id=32964AC1
INFO | jvm 1 | 2017/10/16 14:00:57 | W [a.Manager] [18:00:57]: An alarm could not be acknowledged. It may no longer be registered. Event details: b7b760c2-9839-43f8-9d73-4ddac33ec9d9 / {{ackUser=usr-prov:default:/usr:level1, eventTime=Mon Oct 16 14:00:57 EDT 2017}} request-origin=127.0.0.1, session-user=level1, session-project=UT3DrawTowerHmi, session-id=32964AC1
INFO | jvm 1 | 2017/10/16 14:00:57 | W [a.Manager] [18:00:57]: An alarm could not be acknowledged. It may no longer be registered. Event details: a6490b29-3073-4592-949d-adde96074996 / {{ackUser=usr-prov:default:/usr:level1, eventTime=Mon Oct 16 14:00:57 EDT 2017}} request-origin=127.0.0.1, session-user=level1, session-project=UT3DrawTowerHmi, session-id=32964AC1
INFO | jvm 1 | 2017/10/16 14:00:57 | W [a.Manager] [18:00:57]: An alarm could not be acknowledged. It may no longer be registered. Event details: a3935c2e-9dd6-4469-9522-16c6a88a7691 / {{ackUser=usr-prov:default:/usr:level1, eventTime=Mon Oct 16 14:00:57 EDT 2017}} request-origin=127.0.0.1, session-user=level1, session-project=UT3DrawTowerHmi, session-id=32964AC1
INFO | jvm 1 | 2017/10/16 14:00:57 | W [a.Manager] [18:00:57]: An alarm could not be acknowledged. It may no longer be registered. Event details: b7b760c2-9839-43f8-9d73-4ddac33ec9d9 / {{ackUser=usr-prov:default:/usr:level1, eventTime=Mon Oct 16 14:00:57 EDT 2017}} request-origin=127.0.0.1, session-user=level1, session-project=UT3DrawTowerHmi, session-id=32964AC1
INFO | jvm 1 | 2017/10/16 14:00:57 | W [a.Manager] [18:00:57]: An alarm could not be acknowledged. It may no longer be registered. Event details: a6490b29-3073-4592-949d-adde96074996 / {{ackUser=usr-prov:default:/usr:level1, eventTime=Mon Oct 16 14:00:57 EDT 2017}} request-origin=127.0.0.1, session-user=level1, session-project=UT3DrawTowerHmi, session-id=32964AC1
INFO | jvm 1 | 2017/10/16 14:00:57 | W [a.Manager] [18:00:57]: An alarm could not be acknowledged. It may no longer be registered. Event details: a3935c2e-9dd6-4469-9522-16c6a88a7691 / {{ackUser=usr-prov:default:/usr:level1, eventTime=Mon Oct 16 14:00:57 EDT 2017}} request-origin=127.0.0.1, session-user=level1, session-project=UT3DrawTowerHmi, session-id=32964AC1
INFO | jvm 1 | 2017/10/16 14:00:57 | W [a.Manager] [18:00:57]: An alarm could not be acknowledged. It may no longer be registered. Event details: b7b760c2-9839-43f8-9d73-4ddac33ec9d9 / {{ackUser=usr-prov:default:/usr:level1, eventTime=Mon Oct 16 14:00:57 EDT 2017}} request-origin=127.0.0.1, session-user=level1, session-project=UT3DrawTowerHmi, session-id=32964AC1
INFO | jvm 1 | 2017/10/16 14:00:57 | W [a.Manager] [18:00:57]: An alarm could not be acknowledged. It may no longer be registered. Event details: a6490b29-3073-4592-949d-adde96074996 / {{ackUser=usr-prov:default:/usr:level1, eventTime=Mon Oct 16 14:00:57 EDT 2017}} request-origin=127.0.0.1, session-user=level1, session-project=UT3DrawTowerHmi, session-id=32964AC1
INFO | jvm 1 | 2017/10/16 14:00:57 | W [a.Manager] [18:00:57]: An alarm could not be acknowledged. It may no longer be registered. Event details: a3935c2e-9dd6-4469-9522-16c6a88a7691 / {{ackUser=usr-prov:default:/usr:level1, eventTime=Mon Oct 16 14:00:57 EDT 2017}} request-origin=127.0.0.1, session-user=level1, session-project=UT3DrawTowerHmi, session-id=32964AC1

```

We are using the following script behind a button to acknowledge a collection of alarms.

```auto
# Get a list of all cleared, unacknowledged alarms 
lstClearUnacked = system.alarm.queryStatus(state=["ClearUnacked"])  

if (len(lstClearUnacked) > 0): 	
   # Extract the alarm ID's from all items in the list. 	
   lstAlarmId = [] 	
    for iIndex in range(len(lstClearUnacked)): 	
	    lstAlarmId.append(str(lstClearUnacked[iIndex].getId()))
#end for 	 	

    # Acknowledge all of these alarms (leave the notes field blank). 	
    for iIndex in range(len(lstAlarmId)): 	
	    system.alarm.acknowledge(lstAlarmId, "") 	

#end for #end if

```

We would like to get rid of these Alarm messages and prevent the client HMI from freezing when a large number of alarms are acknowledged with the above script.

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [October 17, 2017, 12:20pm UTC](https://forum.inductiveautomation.com/t/alarm-could-not-be-acknowledged-it-may-no-longer-be-registered/15685/2 "2017-10-17T12:20:39Z")

</div>

Run the script in the background. That is what [system.util.invokeAsynchronous()](https://docs.inductiveautomation.com/display/DOC79/system.util.invokeAsynchronous) is for. Scripts that run in the foreground should always be designed to run in a limited time, preferably less than 1/10 of a second. You might find the functions in later.py helpful, as described in [this thread](http://forum.inductiveautomation.com/t/update-gui-via-asynchronous-thread/9666).

---

<div class="post-metadata">

**Author:** ![hgarner](https://avatars.discourse-cdn.com/v4/letter/h/9d8465/32.png) [@hgarner](https://forum.inductiveautomation.com/u/hgarner)\
**Post date:** [October 17, 2017, 2:31pm UTC](https://forum.inductiveautomation.com/t/alarm-could-not-be-acknowledged-it-may-no-longer-be-registered/15685/3 "2017-10-17T14:31:51Z")

</div>

I imported the later.py functions into my project and used the callAsync function to call the script from a button. It seems to work with a few alarms.

Thanks