# Tag value change event

**URL:** <https://forum.inductiveautomation.com/t/tag-value-change-event/74998>\
**Category:** Ignition\
**Tags:** ignition81\
**Created:** [June 14, 2023, 7:19am UTC](https://forum.inductiveautomation.com/t/tag-value-change-event/74998 "2023-06-14T07:19:43Z")\
**Posts on this page:** 1\
**Showing post:** 4

<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:** [June 14, 2023, 12:24pm UTC](https://forum.inductiveautomation.com/t/tag-value-change-event/74998/4 "2023-06-14T12:24:02Z")

</div>

> [@nminchin](#):
>
> Keep your tag value change scripts extremely fast

This. Events on tags themselves should run in single digit milliseconds or less, due to the likelihood of blocking the system-wide thread pool for tags. That means **no database operations** nor any **network access operations** nor any **recursive searches** in these events.

Gateway tag change events in a project have their own (unbounded) queues and their own threads. Put any time-consuming operations there. But do note that only one thread services all the tags for a given event, so there can be more latency.

---

_[View the full topic](https://forum.inductiveautomation.com/t/tag-value-change-event/74998)._