# Tag Value Changed script does not appear to execute?

**URL:** <https://forum.inductiveautomation.com/t/tag-value-changed-script-does-not-appear-to-execute/78046>\
**Category:** Ignition\
**Tags:** scripting\
**Created:** [August 18, 2023, 2:27am UTC](https://forum.inductiveautomation.com/t/tag-value-changed-script-does-not-appear-to-execute/78046 "2023-08-18T02:27:43Z")\
**Posts on this page:** 4\
**Page:** 2

<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:** [August 28, 2023, 1:16pm UTC](https://forum.inductiveautomation.com/t/tag-value-changed-script-does-not-appear-to-execute/78046/21 "2023-08-28T13:16:46Z")

</div>

> [@MattR](#):
>
> The threshold was increased to prevent this issue from occurring.

That is unlikely to suffice going forward. You and your fellow developers will continue **abusing** tag events until this pops back up. The correct answer is to offload anything that calls out to a database or across a network. Use a gateway event script, or a custom thread pool executor, or, in special cases, an independent thread. (Ignition's store and forward system is ideal for offloading database inserts and updates.)

Regardless, you should be instrumenting your tag events with java's System.nanoTime() and logging detailed warnings for anything that takes 10ms or more.

Some reading for you:

[https://forum.inductiveautomation.com/search?q=tag%20event%20thread%20pool%20blocked%20order%3Alatest](https://forum.inductiveautomation.com/search?q=tag%20event%20thread%20pool%20blocked%20order%3Alatest)

---

<div class="post-metadata">

**Author:** ![MattR](https://avatars.discourse-cdn.com/v4/letter/m/2acd7d/32.png) [@MattR](https://forum.inductiveautomation.com/u/MattR)\
**Post date:** [August 28, 2023, 1:32pm UTC](https://forum.inductiveautomation.com/t/tag-value-changed-script-does-not-appear-to-execute/78046/22 "2023-08-28T13:32:32Z")

</div>

Thanks for the info Phil. It is not the intent to abuse the tag event. However, this is a project we were asked to work on that was inherited from another company. It utilized large UDTs with extensive use of tag event scripts. A complete re-development of the existing system would have been necessary to correct this (not an option). It was our (bad) luck to be the ones to hit this limit. This is something I will remember in the future...

---

<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:** [August 28, 2023, 1:34pm UTC](https://forum.inductiveautomation.com/t/tag-value-changed-script-does-not-appear-to-execute/78046/23 "2023-08-28T13:34:11Z")

</div>

Do share this forum topic with your client, then, so they know to be wary of the long-term stability of projects from the other company. /:

---

<div class="post-metadata">

**Author:** ![MattR](https://avatars.discourse-cdn.com/v4/letter/m/2acd7d/32.png) [@MattR](https://forum.inductiveautomation.com/u/MattR)\
**Post date:** [August 28, 2023, 1:36pm UTC](https://forum.inductiveautomation.com/t/tag-value-changed-script-does-not-appear-to-execute/78046/24 "2023-08-28T13:36:28Z")

</div>

Early in the effort, I shared a link to this forum. I will be sure to pass on the info you just provided. Thank you.

[Previous page](https://forum.inductiveautomation.com/t/tag-value-changed-script-does-not-appear-to-execute/78046.md?page=1)