# Transaction Group executes twice, even though OPC value changes once

**URL:** <https://forum.inductiveautomation.com/t/transaction-group-executes-twice-even-though-opc-value-changes-once/73548>\
**Category:** Ignition\
**Tags:** perspective\
**Created:** [May 10, 2023, 4:34pm UTC](https://forum.inductiveautomation.com/t/transaction-group-executes-twice-even-though-opc-value-changes-once/73548 "2023-05-10T16:34:16Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Marc.Akoto](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/marc.akoto/32/19291_2.png) [@Marc.Akoto](https://forum.inductiveautomation.com/u/Marc.Akoto)\
**Post date:** [May 10, 2023, 4:34pm UTC](https://forum.inductiveautomation.com/t/transaction-group-executes-twice-even-though-opc-value-changes-once/73548/1 "2023-05-10T16:34:17Z")

</div>

Hi,

I have a Transaction Group which executes twice, even though the trigger is set to a OPC value which only changed once. This results in a duplicate insert in the database

Here is what I already did :

- Transaction Group Execution Scheduling (1s): I increased to 2s instead of 1s but not better
- Tag Group Rate (1s): I reduced to 500ms instead of 1s but not better
- the device itself: simulator, OPC, no visible duplicate change on the value/timestamp/quality

Now I'm suspecting something with the Latched/Source values :  
is source value changing before execution/insert of the latched value ?

- Is there a way to configure the latch time ?
- Is there a way to force the trigger to execute once only ?
- Any other idea to fix this issue please ?

For info, I'm using the following :  
- Ignition 8.1.26 + MySQL8.0.22  
- the template project "oee\_downtime" in this exchange resource "Perspective Equipment Schedule" [Ignition Exchange | Inductive Automation](https://www.inductiveautomation.com/exchange/2143/overview)

Thanks in advance

 ![trigger tab + Transaction Group Items](https://us1.discourse-cdn.com/inductiveautomation/original/3X/b/9/b9d7a1999b13eb0e8019812bf387d713f3fabaee.png)

 ![action tab](https://us1.discourse-cdn.com/inductiveautomation/original/3X/f/b/fbabdeea6aaff45252245f7ee404c2db4d555337.png)

![SQL duplicate inserts](https://us1.discourse-cdn.com/inductiveautomation/original/3X/0/a/0a1e5fe7749a4663d8276343b99388dd6fd564c0.png)

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [May 10, 2023, 6:24pm UTC](https://forum.inductiveautomation.com/t/transaction-group-executes-twice-even-though-opc-value-changes-once/73548/2 "2023-05-10T18:24:08Z")

</div>

Just to cover the bases...

Any project inheritance going on?  
Any chance someone took a gateway backup or project export and restored it on their own system?

---

<div class="post-metadata">

**Author:** ![JordanCClark](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jordancclark/32/83362_2.png) [@JordanCClark](https://forum.inductiveautomation.com/u/JordanCClark)\
**Post date:** [May 10, 2023, 6:26pm UTC](https://forum.inductiveautomation.com/t/transaction-group-executes-twice-even-though-opc-value-changes-once/73548/3 "2023-05-10T18:26:16Z")

</div>

Or, are there two transaction groups pointing to the same table?

---

<div class="post-metadata">

**Author:** ![Marc.Akoto](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/marc.akoto/32/19291_2.png) [@Marc.Akoto](https://forum.inductiveautomation.com/u/Marc.Akoto)\
**Post date:** [May 11, 2023, 1:08pm UTC](https://forum.inductiveautomation.com/t/transaction-group-executes-twice-even-though-opc-value-changes-once/73548/4 "2023-05-11T13:08:07Z")

</div>

Indeed it was a project backup conflicting with the same transaction groups. That was basic.  
Thanks @paul-griffith and @JordanCClark !