Best practices and pitfalls with Tag Event Scrips

[pturmel]

They don't take a thread from the three-thread pool used by the tag events subsystem, but borrow a thread from the tag subsystem itself, I think. (You could deliberately throw some exceptions in a callback to investigate the thread origin.)

Use a gateway tag event script (in the project) for the heavy workload requirements. If there is some detail of the situation that requires they be tag valueChange events, consider this technique:

Java concurrent queue for tag change scripts

Continuing the discussion from [SOLVED] Are tag Value Changed scripts running asynchronously?: 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 …