# Transaction Group Triggering When Value Has Not Changed

**URL:** <https://forum.inductiveautomation.com/t/transaction-group-triggering-when-value-has-not-changed/96260>\
**Category:** Ignition\
**Tags:** ignition81\
**Created:** [September 20, 2024, 8:57pm UTC](https://forum.inductiveautomation.com/t/transaction-group-triggering-when-value-has-not-changed/96260 "2024-09-20T20:57:49Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Pico\_Sankari](https://avatars.discourse-cdn.com/v4/letter/p/aeb1de/32.png) [@Pico\_Sankari](https://forum.inductiveautomation.com/u/Pico_Sankari)\
**Post date:** [September 20, 2024, 8:57pm UTC](https://forum.inductiveautomation.com/t/transaction-group-triggering-when-value-has-not-changed/96260/1 "2024-09-20T20:57:49Z")

</div>

I have a simple transaction group:

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/7/8/7883c30de5c04b495798499bd69d91730fb232c8.png)  
This is one tag that is either true or false. This morning, something very briefly interrupted the connection and it wrote the same value twice:  
 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/8/b/8b34bf778be63c350ee9848a8e4b2e7ef2368dbe.png)  
Is there any way to prevent this?  
I know that this could be caused by making an edit and resaving the transaction group, but this is not the case. I can see that there was some sort of disconnect on the gateway at the same time from the CPU usage:  
 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/4/3/43ba7164f19bb7df8910fc87ea92d6726d6d3aa4.png)  
Would also be open to suggestions for preventing this.