# Ignition tag change script help **URL:** \ **Category:** Ignition\ **Tags:** perspective\ **Created:** [January 21, 2026, 9:59pm UTC](https://forum.inductiveautomation.com/t/ignition-tag-change-script-help/113462 "2026-01-21T21:59:49Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![ryan.white](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/ryan.white/32/73193_2.png) [@ryan.white](https://forum.inductiveautomation.com/u/ryan.white)\ **Post date:** [January 21, 2026, 10:35pm UTC](https://forum.inductiveautomation.com/t/ignition-tag-change-script-help/113462/2 "2026-01-21T22:35:11Z")
Looks like you might have messed up the preformatted text formatting, see [Wiki - how to post code on this forum](https://forum.inductiveautomation.com/t/wiki-how-to-post-code-on-this-forum/77831). > [@Nathaniel\_Webb](#): > > This may be due to my transaction group falling sending after my tag change script runs You need to guarantee that the transaction group runs and completes before you trigger the table refresh. You are ending up with a race condition between your transaction group and your query against the DB for the latest records. The only way to guarantee ordering is to script your transaction in a [Gateway Tag Change event](https://www.docs.inductiveautomation.com/docs/8.1/platform/scripting/scripting-in-ignition/gateway-event-scripts#tag-change-scripts), and at the end of the transaction script, use `system.util.sendMessage` to send a message aimed at the project where this view resides. From there, in the [Session Message Handler](https://www.docs.inductiveautomation.com/docs/8.1/ignition-modules/perspective/scripting-in-perspective/perspective-session-events-scripts#message), use `system.perspective.sendMessage` with a session scope to trigger the table refresh. Adjust your table message handler to listen at the session level. --- _[View the full topic](https://forum.inductiveautomation.com/t/ignition-tag-change-script-help/113462)._