# Currently running Scripts On Ignition Gateway

**URL:** <https://forum.inductiveautomation.com/t/currently-running-scripts-on-ignition-gateway/112739>\
**Category:** Ignition\
**Tags:** vision\
**Created:** [December 10, 2025, 5:40pm UTC](https://forum.inductiveautomation.com/t/currently-running-scripts-on-ignition-gateway/112739 "2025-12-10T17:40:28Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Varsha\_Gottipati1](https://avatars.discourse-cdn.com/v4/letter/v/ce73a5/32.png) [@Varsha\_Gottipati1](https://forum.inductiveautomation.com/u/Varsha_Gottipati1)\
**Post date:** [December 10, 2025, 5:40pm UTC](https://forum.inductiveautomation.com/t/currently-running-scripts-on-ignition-gateway/112739/1 "2025-12-10T17:40:28Z")

</div>

![Screenshot 2025-12-10 093440](https://us1.discourse-cdn.com/inductiveautomation/original/3X/4/4/4438422431be7bed771eeaf1bb2ae76f0582515d.png)

What would happen if I hit on cancel? Can someone please help me understand the purpose of this diagnostics?

---

<div class="post-metadata">

**Author:** ![Ryan\_Deardorff](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/ryan_deardorff/32/63815_2.png) [@Ryan\_Deardorff](https://forum.inductiveautomation.com/u/Ryan_Deardorff)\
**Post date:** [December 10, 2025, 5:50pm UTC](https://forum.inductiveautomation.com/t/currently-running-scripts-on-ignition-gateway/112739/2 "2025-12-10T17:50:48Z")

</div>

The script would stop running.

What are those scripts doing that could possibly take 2 days? Are they running an infinite loop?

---

<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:** [December 10, 2025, 10:43pm UTC](https://forum.inductiveautomation.com/t/currently-running-scripts-on-ignition-gateway/112739/3 "2025-12-10T22:43:34Z")

</div>

I had a couple that did this. They were reaching out to a url with `system.net.httpClient().get()` and the internet died and came back, but for some reason they didn’t produce a timeout exception and just sat there… There’s a relatively short default timeout, but it didn’t respect it. I had to supply it (`system.net.httpClient().get(timeout=10000)`) which I _think_ has fixed it… time will tell

> [@Varsha\_Gottipati1](#):
>
> Can someone please help me understand the purpose of this diagnostics?

The purpose is to be able to see what timer scripts are running, to find issues like this one.

Before you cancel them, I would be taking a thread dump so that you can see what’s holding them up. Use Kindling to open the dump and find those thread ids in there. The stack trace will tell you, or IA, or us, what it’s stuck on
