# 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:** 1\
**Showing post:** 2

<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).

---

_[View the full topic](https://forum.inductiveautomation.com/t/alarm-could-not-be-acknowledged-it-may-no-longer-be-registered/15685)._