# Passing transaction group SQL error to screen **URL:** \ **Category:** Ignition\ **Created:** [December 13, 2021, 4:22am UTC](https://forum.inductiveautomation.com/t/passing-transaction-group-sql-error-to-screen/54030 "2021-12-13T04:22:32Z")\ **Posts on this page:** 1\ **Showing post:** 2
**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:** [December 13, 2021, 4:27am UTC](https://forum.inductiveautomation.com/t/passing-transaction-group-sql-error-to-screen/54030/2 "2021-12-13T04:27:01Z")
If you can have such execution problems, I would re-implement the transaction group as a gateway tag change script. Within a script, you can capture then do whatever you like with exceptions. Edit: See "case 3" in this topic for ideas: > [@Missed gateway tag change events/split separated strings into individual tags](https://forum.inductiveautomation.com/t/missed-gateway-tag-change-events-split-separated-strings-into-individual-tags/42705/7): > > Ok. I use multiple techniques depending on the client’s needs and trust in hardware at various points along the chain. In all cases, I avoid triggering on booleans, and I avoid writing any given value from more than one direction. I like to use small integers as triggers–increment to trigger, rolling over naturally, but skipping zero. Sometimes an LINT timestamp is a natural trigger (Logix UTC wallclock µs or Omron clock ns, perhaps). Case 1: Fire and Forget Sometimes one just wants produc… --- _[View the full topic](https://forum.inductiveautomation.com/t/passing-transaction-group-sql-error-to-screen/54030)._