# Delay in Tag Event Script (Value Changed)

**URL:** <https://forum.inductiveautomation.com/t/delay-in-tag-event-script-value-changed/70666>\
**Category:** Ignition\
**Tags:** ignition81, scripting\
**Created:** [March 6, 2023, 1:19pm UTC](https://forum.inductiveautomation.com/t/delay-in-tag-event-script-value-changed/70666 "2023-03-06T13:19:47Z")\
**Posts on this page:** 1\
**Showing post:** 6

<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:** [March 6, 2023, 4:33pm UTC](https://forum.inductiveautomation.com/t/delay-in-tag-event-script-value-changed/70666/6 "2023-03-06T16:33:26Z")

</div>

In general, any delays of any kind are not acceptable in tag value change scripts, or any other tag event, due to the shared execution thread pool. Don't do it. You will bog down your tag infrastructure.

Instead, design a state machine, perhaps with a timestamp in a memory tag, that is updated by a regular timer event. Do not use jython time, thread, or sleeping functionality in such events (or anywhere in Ignition, really).

---

_[View the full topic](https://forum.inductiveautomation.com/t/delay-in-tag-event-script-value-changed/70666)._