# When are transaction groups the best solution? **URL:** \ **Category:** Ignition\ **Created:** [April 11, 2025, 11:48pm UTC](https://forum.inductiveautomation.com/t/when-are-transaction-groups-the-best-solution/105025 "2025-04-11T23:48:52Z")\ **Posts on this page:** 1\ **Showing post:** 4
**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:** [April 12, 2025, 12:12am UTC](https://forum.inductiveautomation.com/t/when-are-transaction-groups-the-best-solution/105025/4 "2025-04-12T00:12:46Z")
Perhaps you are ready for the rabbit hole. Start here: > [@\[SOLVED\] Are tag Value Changed scripts running asynchronously?](https://forum.inductiveautomation.com/t/solved-are-tag-value-changed-scripts-running-asynchronously/68704/5): > > If it absolutely has to be a tag event, consider calling into a script module that will submit the event to a java concurrent queue, then run a timer event with a dedicated thread to drain the queue and loop through the queued events. Then this: > [@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 … And this: > [@Modbus Slave/Server to Generate Read Only Tags](https://forum.inductiveautomation.com/t/modbus-slave-server-to-generate-read-only-tags/87583/21): > > I've create a generic "Modbus Publish" script that eliminates the need for a second set of tags. I've publicly posted it here: [https://www.automation-pros.com/ignition/modbusPublish.py](https://www.automation-pros.com/ignition/modbusPublish.py) It requires the "Queue Utility" script posted here: [https://www.automation-pros.com/ignition/queueUtil.py](https://www.automation-pros.com/ignition/queueUtil.py) and described over here: Both scripts rely on my Integration Toolkit's globalVarMap() script function, but you can rework that (not quite 1:1) to use system.util.getGlobals() if you must. (Not recomme… And finally this: > [@Automation Professionals' Integration Toolkit Module](https://forum.inductiveautomation.com/t/automation-professionals-integration-toolkit-module/74934/212): > > Meanwhile.... Automation Professionals is pleased to announce a BETA release of this module, with a significant new feature: Tag Actors. For Ignition v8.1+: v2.1.0.250841756 The details of the new functionality are in the freshly updated documentation, under [Tag Actors](https://www.automation-pros.com/toolkit/doc/actors.html). The Republish action provides a built-in alternative to the Modbus Publishing algorithm I recommend over here: The Republish action can also be used with expression tags to revive the old OPC writeback functionality, witho… --- _[View the full topic](https://forum.inductiveautomation.com/t/when-are-transaction-groups-the-best-solution/105025)._