# Killing Gateway Scripts Via Scripting

**URL:** <https://forum.inductiveautomation.com/t/killing-gateway-scripts-via-scripting/51674>\
**Category:** Ignition\
**Tags:** ignition81, scripting\
**Created:** [October 6, 2021, 7:54pm UTC](https://forum.inductiveautomation.com/t/killing-gateway-scripts-via-scripting/51674 "2021-10-06T19:54:28Z")\
**Posts on this page:** 1\
**Showing post:** 2

<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:** [October 6, 2021, 7:58pm UTC](https://forum.inductiveautomation.com/t/killing-gateway-scripts-via-scripting/51674/2 "2021-10-06T19:58:38Z")

</div>

> [@Thread Descriptions in Diagnostics Menu](https://forum.inductiveautomation.com/t/thread-descriptions-in-diagnostics-menu/36264/2):
>
> For the first request, changes are coming soon - possibly as soon as 8.0.15. Right now, there’s no way to set that description, but there will just be a description keyword argument to provide on your system.util.invokeAsynchronous calls. For the latter: from com.inductiveautomation.ignition.common.script import ScriptManager for script in ScriptManager.executingScripts(): if script.description == "My Async Thread": ScriptManager.interrupt(script.threadId)

In addition to the `threadId`, each element in the `executingScripts()` list will have a `startTime` long timestamp.

---

_[View the full topic](https://forum.inductiveautomation.com/t/killing-gateway-scripts-via-scripting/51674)._