# Transaction Group Execution Order

**URL:** <https://forum.inductiveautomation.com/t/transaction-group-execution-order/6622>\
**Category:** Ignition\
**Created:** [May 31, 2013, 6:59pm UTC](https://forum.inductiveautomation.com/t/transaction-group-execution-order/6622 "2013-05-31T18:59:25Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![ErikG](https://avatars.discourse-cdn.com/v4/letter/e/91b2a8/32.png) [@ErikG](https://forum.inductiveautomation.com/u/ErikG)\
**Post date:** [May 31, 2013, 6:59pm UTC](https://forum.inductiveautomation.com/t/transaction-group-execution-order/6622/1 "2013-05-31T18:59:25Z")

</div>

Is there a way to determine the order that the Transaction Groups execute?

For example, I have some transaction groups that Insert, and others that Update. While the trigger is active for the Insert groups (one scan), I don’t want the Update groups to run.

Or if they do run, at least run AFTER the Insert groups.

---

<div class="post-metadata">

**Author:** ![Robert.McKenzie](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/robert.mckenzie/32/4134_2.png) [@Robert.McKenzie](https://forum.inductiveautomation.com/u/Robert.McKenzie)\
**Post date:** [June 27, 2013, 11:55pm UTC](https://forum.inductiveautomation.com/t/transaction-group-execution-order/6622/2 "2013-06-27T23:55:54Z")

</div>

This is sometimes a bit hard to guarantee. I recommend using the ‘Write handshake on success’ to set the trigger for the next group.

---

<div class="post-metadata">

**Author:** ![ErikG](https://avatars.discourse-cdn.com/v4/letter/e/91b2a8/32.png) [@ErikG](https://forum.inductiveautomation.com/u/ErikG)\
**Post date:** [July 22, 2013, 7:59pm UTC](https://forum.inductiveautomation.com/t/transaction-group-execution-order/6622/3 "2013-07-22T19:59:13Z")

</div>

Thanks for the reply.  
Ultimately we decided to write a custom Where clause on the Update Group to prevent this scenario from occurring.