# Scheduled transaction group stopped at end of DST

**URL:** <https://forum.inductiveautomation.com/t/scheduled-transaction-group-stopped-at-end-of-dst/7488>\
**Category:** Ignition\
**Created:** [October 29, 2013, 2:43pm UTC](https://forum.inductiveautomation.com/t/scheduled-transaction-group-stopped-at-end-of-dst/7488 "2013-10-29T14:43:16Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![chi](https://avatars.discourse-cdn.com/v4/letter/c/0ea827/32.png) [@chi](https://forum.inductiveautomation.com/u/chi)\
**Post date:** [October 29, 2013, 2:43pm UTC](https://forum.inductiveautomation.com/t/scheduled-transaction-group-stopped-at-end-of-dst/7488/1 "2013-10-29T14:43:16Z")

</div>

I have a scheduled transaction group that stopped executing at midnight after daylight saving time ended.  
End of DST was on Sunday 27, 02am, the last group execution was at 00:02am on the 28. The group executed without problems for months before.  
[attachment=0]GroupSchedule.png[/attachment]

Igniton Version is 7.5.6.

---

<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:** [December 26, 2013, 10:03pm UTC](https://forum.inductiveautomation.com/t/scheduled-transaction-group-stopped-at-end-of-dst/7488/2 "2013-12-26T22:03:15Z")

</div>

That sounds pretty unusual that it would stop 23 hours after daylight savings time ended. Is there anything in the wrapper.log file around that time? Has the group worked since then?

---

<div class="post-metadata">

**Author:** ![chi](https://avatars.discourse-cdn.com/v4/letter/c/0ea827/32.png) [@chi](https://forum.inductiveautomation.com/u/chi)\
**Post date:** [December 30, 2013, 10:32am UTC](https://forum.inductiveautomation.com/t/scheduled-transaction-group-stopped-at-end-of-dst/7488/3 "2013-12-30T10:32:44Z")

</div>

Hi Robert,

thanks for your reply. I did some tests with 7.6.4 in the last days, and the problem is still reproduceable.  
To test, i disabled the time synchronization in the VM and set the date manually while the Ignition service was stopped. The gateways timezone is Europe/Prague [GMT+1:00].

On Sun, Oct 27 2013 (end of DST in Germany) the group skips the additional hour and misses a full day after midnight:  
LastExec: Sun Oct 27 01:32:00 CEST Next Exec.: Sun Oct 27 01:47:00 CEST  
LastExec: Sun Oct 27 01:47:00 CEST Next Exec.: Sun Oct 27 02:02:00 CET  
At this point, the schedule uses CET instead of CEST, so the next four execs in the additional hour are skipped.  
The next execution is at   
LastExec: Sun Oct 27 02:02:00 CET Next Exec.: Sun Oct 27 02:17:00 CET  
After that, the group runs till  
LastExec: Sun Oct 27 23:47:00 CET Next Exec.: Mon Oct 28 23:02:00 CET  
so here the execution stops for a full day. This happens only on this special date and is also reproduceable if the group is restarted.[attachment=2]group\_dst\_end.png[/attachment]  
When DST starts, there`s also a problem at next midnight. Here, the group skips one hour.[attachment=1]group\_dst\_start.png[/attachment]

There is also a random bug that shows sometimes after a gateway restart. The group is executed one second early and the ‘Next Execution’ field in the status display shows a wrong value. The group still operates, but is always a second early. After stopping and starting, the group works as expected.[attachment=0]group\_after\_gateway\_restart.png[/attachment]

Let me know if you need more information to reproduce this in your system.  
Regards,  
Carsten

---

<div class="post-metadata">

**Author:** ![chi](https://avatars.discourse-cdn.com/v4/letter/c/0ea827/32.png) [@chi](https://forum.inductiveautomation.com/u/chi)\
**Post date:** [January 15, 2014, 5:19pm UTC](https://forum.inductiveautomation.com/t/scheduled-transaction-group-stopped-at-end-of-dst/7488/4 "2014-01-15T17:19:46Z")

</div>

Any progress on this? Last weekend of march is coming closer…

---

<div class="post-metadata">

**Author:** ![Colby.Clegg](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/colby.clegg/32/3282_2.png) [@Colby.Clegg](https://forum.inductiveautomation.com/u/Colby.Clegg)\
**Post date:** [January 17, 2014, 10:16pm UTC](https://forum.inductiveautomation.com/t/scheduled-transaction-group-stopped-at-end-of-dst/7488/5 "2014-01-17T22:16:04Z")

</div>

Hi,

Thanks for the details. I just saw this thread, and will look into it soon. I expect we can get something worked out before 7.6.5.

Regards,

---

<div class="post-metadata">

**Author:** ![Colby.Clegg](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/colby.clegg/32/3282_2.png) [@Colby.Clegg](https://forum.inductiveautomation.com/u/Colby.Clegg)\
**Post date:** [February 11, 2014, 7:52pm UTC](https://forum.inductiveautomation.com/t/scheduled-transaction-group-stopped-at-end-of-dst/7488/6 "2014-02-11T19:52:01Z")

</div>

Hi,

We’ve made a few adjustments, and I’m going to have QA set up a VM to verify before and after, in addition to the unit tests that I’ve been using. We still should be able to get it in for the 7.6.5 release.

Regards,

---

<div class="post-metadata">

**Author:** ![chi](https://avatars.discourse-cdn.com/v4/letter/c/0ea827/32.png) [@chi](https://forum.inductiveautomation.com/u/chi)\
**Post date:** [March 20, 2014, 4:46pm UTC](https://forum.inductiveautomation.com/t/scheduled-transaction-group-stopped-at-end-of-dst/7488/7 "2014-03-20T16:46:11Z")

</div>

Hi,

any news? Only 10 days left and there’s nothing in the 7.6.5 changelog…

---

<div class="post-metadata">

**Author:** ![Colby.Clegg](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/colby.clegg/32/3282_2.png) [@Colby.Clegg](https://forum.inductiveautomation.com/u/Colby.Clegg)\
**Post date:** [March 20, 2014, 5:31pm UTC](https://forum.inductiveautomation.com/t/scheduled-transaction-group-stopped-at-end-of-dst/7488/8 "2014-03-20T17:31:19Z")

</div>

Some changes where made, but I don’t think this particular problem was fixed. We discovered late in testing that there was still a problem.

The best option for now is to probably change the group to not run on a schedule, and instead create a boolean, run-always expression tag, and set the group to use that as a trigger (\>0, only execute once), with the expression:

```auto
(dateExtract(now(),"min") % 15)=0
```

You can set the group to run every second or so to check the trigger.

Sorry that we didn’t get it taken care of…

---

<div class="post-metadata">

**Author:** ![fadihindi](https://avatars.discourse-cdn.com/v4/letter/f/34f0e0/32.png) [@fadihindi](https://forum.inductiveautomation.com/u/fadihindi)\
**Post date:** [November 6, 2014, 1:16am UTC](https://forum.inductiveautomation.com/t/scheduled-transaction-group-stopped-at-end-of-dst/7488/9 "2014-11-06T01:16:31Z")

</div>

I have this exact issue happening on a couple of Ignition gateways. I have one transaction group configured to execute at 00:00 every day, and a second group at 00:05 every day. They execute as scheduled the day of the end of DST (i.e., DST end at 02:00 AM on 11/02/14 and their last execution was at 00:00 and 00:05 on 11/02/14). After that they just stop executing. However I have another gateway configured with the same transaction groups whose system time is configured to NOT be automatically adjusted for daylight savings time, and the issue did not occur. All groups have been executing as normal. These are Windows 7 x64 machines. Does this provide any clues as to what might be happening?

---

<div class="post-metadata">

**Author:** ![Colby.Clegg](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/colby.clegg/32/3282_2.png) [@Colby.Clegg](https://forum.inductiveautomation.com/u/Colby.Clegg)\
**Post date:** [November 6, 2014, 4:40pm UTC](https://forum.inductiveautomation.com/t/scheduled-transaction-group-stopped-at-end-of-dst/7488/10 "2014-11-06T16:40:26Z")

</div>

Hi,

What version of Ignition are you using? The most recent changes for this problem were made for 7.6.7 (and therefore should also be in 7.7).

Regards,

---

<div class="post-metadata">

**Author:** ![Liliya\_Boyadjieva1](https://avatars.discourse-cdn.com/v4/letter/l/5f8ce5/32.png) [@Liliya\_Boyadjieva1](https://forum.inductiveautomation.com/u/Liliya_Boyadjieva1)\
**Post date:** [March 25, 2024, 5:56pm UTC](https://forum.inductiveautomation.com/t/scheduled-transaction-group-stopped-at-end-of-dst/7488/11 "2024-03-25T17:56:09Z")

</div>

Has any official fix been made for this? This happened to us on March 10th of this year on a transaction group scheduled to trigger at exactly 2:00 AM. We were able to get it to run again by changing the trigger time.

---

<div class="post-metadata">

**Author:** ![Gomez](https://avatars.discourse-cdn.com/v4/letter/g/d78d45/32.png) [@Gomez](https://forum.inductiveautomation.com/u/Gomez)\
**Post date:** [July 26, 2025, 3:11pm UTC](https://forum.inductiveautomation.com/t/scheduled-transaction-group-stopped-at-end-of-dst/7488/13 "2025-07-26T15:11:01Z")

</div>

Same problem was present on 7.9.11. When a transaction is scheduled and there is a change on daylight saving settings. Need to disable and reenable the transaction. Is there at least a way to monitor the status of a transaction? Like a system folder with some stats information just to raise an alarm? I think it could be a really usufull function ( or also a boolean tag to enable or disable a transactin group )
