# Transaction group is entering duplicate rows in table

**URL:** <https://forum.inductiveautomation.com/t/transaction-group-is-entering-duplicate-rows-in-table/34769>\
**Category:** Ignition\
**Tags:** ignition79\
**Created:** [May 14, 2020, 11:29pm UTC](https://forum.inductiveautomation.com/t/transaction-group-is-entering-duplicate-rows-in-table/34769 "2020-05-14T23:29:09Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![jfryar](https://avatars.discourse-cdn.com/v4/letter/j/8e8cbc/32.png) [@jfryar](https://forum.inductiveautomation.com/u/jfryar)\
**Post date:** [May 14, 2020, 11:29pm UTC](https://forum.inductiveautomation.com/t/transaction-group-is-entering-duplicate-rows-in-table/34769/1 "2020-05-14T23:29:10Z")

</div>

I have a few transaction groups that are supposed to be running once per day. This table is used in some custom reports. But 5 or 6 times a month I find duplicate entries in the table.

I have the transaction group setup to run once per day. It does this by having the “Excecution Scheduling” set to timer at 1 second intervals. There is a “Run-Always Expression Items” trigger that is an expression and checks to see if the current time is within the 3 a.m. hour and if it is then evaluates to true. Within the Trigger tab of the transaction group I have the “Only execute once while trigger is active” option checked. As I understand it this should cause it to execute once a day within the 3 a.m. hour. But I’m still getting duplicate rows in the table every so often.

I can’t seem to find the circumstance that causes the duplicates. I wonder if it happens when the gateway is restarted. Most of the time there is also a 3rd entry for the same timestamp in the table where everything except the timestamp is null. It would look something like this…

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/2X/7/783980105a263f1bab39b600dd9649e6d38fa93e.png)

See below for settings for the transaction group.

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/2X/2/2c78a8e50245df3adaa87729ba3645e4ec2c6db0.png)

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/2X/e/e9506264595871462c206e77101193e06615339a.png)

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/2X/7/70fa771fab09d9ca84196c0b0b24d54c6a47c341.png)

![image](https://us1.discourse-cdn.com/inductiveautomation/original/2X/a/a6604f6aca5572a1e1ddbfc80de5f7fc030b75df.png)

---

<div class="post-metadata">

**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:** [May 15, 2020, 12:15am UTC](https://forum.inductiveautomation.com/t/transaction-group-is-entering-duplicate-rows-in-table/34769/2 "2020-05-15T00:15:06Z")

</div>

Is there any reason you didn’t just use the “Schedule” option (instead of Timer) and have it run at 3am (with no repeat)?

---

<div class="post-metadata">

**Author:** ![jfryar](https://avatars.discourse-cdn.com/v4/letter/j/8e8cbc/32.png) [@jfryar](https://forum.inductiveautomation.com/u/jfryar)\
**Post date:** [May 15, 2020, 12:28am UTC](https://forum.inductiveautomation.com/t/transaction-group-is-entering-duplicate-rows-in-table/34769/3 "2020-05-15T00:28:00Z")

</div>

No reason that I can think of. But I’m not the one that set it up. Most of our transaction groups are setup this way. I don’t know why we don’t use the schedule instead of a timer. I assumed perhaps there is a glitch or something this method avoids.

This particular client is running 7.9.13