# Gateway Events: Tag Change **URL:** \ **Category:** Ignition\ **Created:** [January 6, 2025, 8:29pm UTC](https://forum.inductiveautomation.com/t/gateway-events-tag-change/100499 "2025-01-06T20:29:37Z")\ **Posts on this page:** 1\ **Showing post:** 3
**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:** [January 6, 2025, 9:29pm UTC](https://forum.inductiveautomation.com/t/gateway-events-tag-change/100499/3 "2025-01-06T21:29:19Z")
This is one of the situations where I recommend the combination of tag valueChange events that delegate to a queue drained by one or more timer events. As described here: > [@Java concurrent queue for tag change scripts](https://forum.inductiveautomation.com/t/java-concurrent-queue-for-tag-change-scripts/82044): > > Continuing the discussion from [[SOLVED] Are tag Value Changed scripts running asynchronously?](https://forum.inductiveautomation.com/t/solved-are-tag-value-changed-scripts-running-asynchronously/68704/5): We've got code in our standard library that I need to log a value change on a tag and then associate various data points with that value change. The value is located in a UDT, and because this is part of our "standard" library we use for our customers, the number of tags is variable and quite possibly numerous so having a gateway tag event script isn't feasible for this solution. I was reading up on … --- _[View the full topic](https://forum.inductiveautomation.com/t/gateway-events-tag-change/100499)._