I have several transaction groups storing data at shift’s end every day. It has been working without issues, but in the last days, the group executes one hour before the scheduled time. Is there someplace where the SQL Bridge time may have changed?
All the scheduled scripts work on the right time, only the transaction groups have this offset.
Maybe a datetime setting or time zone difference between the Ignition server and your DB server?
Whatever it is, I usually have a shift active tag (boolean) and use that tag to trigger instead of a schedule. If the schedule ever changes, modify the shift active expression or script and all your transaction groups will follow without need to reconfigure each one.
Thanks, I thought about timezone, but both servers have the same one. I guess the triggered execution will be the best solution, but I can understand what’s happening, that would be great. Also, I’d rather not go through all these transaction groups changing them to triggered.
Check the current time on your gateway and run select now() in a query to see if they match. You said you checked TZ settings but did not say whether the current time matched.
the current time matches to the second, I’ve checked with queries and scripts. The timestamp on database gives the right time; just these transaction groups are off.
I have other transaction groups on the same table executing every minute, and they get the scheduled time right.
Thank you
I’m not sure then, maybe someone else will chime in.
