# Behavior of Threads in Client Timer Event Script

**URL:** <https://forum.inductiveautomation.com/t/behavior-of-threads-in-client-timer-event-script/110481>\
**Category:** Ignition\
**Tags:** vision, scripting\
**Created:** [September 9, 2025, 12:00pm UTC](https://forum.inductiveautomation.com/t/behavior-of-threads-in-client-timer-event-script/110481 "2025-09-09T12:00:43Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [September 9, 2025, 12:39pm UTC](https://forum.inductiveautomation.com/t/behavior-of-threads-in-client-timer-event-script/110481/2 "2025-09-09T12:39:36Z")

</div>

> [@wingram](#):
>
> For example, is the Scripting module being recompiled? Does the JVM kill the existing threads?

No, neither of these.

> [@wingram](#):
>
> Or do threads stack up in the background every time the main() function is called, and all processes aren’t completed?

No. The behavior depends on whether it's fixed delay or fixed rate, but:

> [@Continuous running scripts](https://forum.inductiveautomation.com/t/continuous-running-scripts/104525/10):
>
> In "Fixed Delay", your script runs again at whatever the interval is _after_ the execution finishes.
> 
> In "Fixed Rate", your script runs at the fixed interval, but if an execution goes long it does not overlap, the next execution just begins immediately after the previous finishes.

Only one instance will be executing at any given time.

---

_[View the full topic](https://forum.inductiveautomation.com/t/behavior-of-threads-in-client-timer-event-script/110481)._