# Tag Value Change Scripts: Are They Run Asynchronously?

**URL:** <https://forum.inductiveautomation.com/t/tag-value-change-scripts-are-they-run-asynchronously/53749>\
**Category:** Ignition\
**Tags:** ignition79, ignition81\
**Created:** [December 3, 2021, 7:12pm UTC](https://forum.inductiveautomation.com/t/tag-value-change-scripts-are-they-run-asynchronously/53749 "2021-12-03T19:12:57Z")\
**Posts on this page:** 1\
**Showing post:** 9

<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:** [December 3, 2021, 7:35pm UTC](https://forum.inductiveautomation.com/t/tag-value-change-scripts-are-they-run-asynchronously/53749/9 "2021-12-03T19:35:01Z")

</div>

Yes, there’s also a thread pool of size 3 that is shared between all tag event executions. This really only matters in the case you have a lot of slow to execute scripts, as @pturmel mentioned.

Sometimes it’s okay to increase this pool size, but more often it means you’ve done something wrong and should rethink your approach.

---

_[View the full topic](https://forum.inductiveautomation.com/t/tag-value-change-scripts-are-they-run-asynchronously/53749)._
