I have a transaction group that is set up to run on a Schedule at 06:17 every day, and it logs data to my SQL server database. As I looked at it this morning, I can see that in the Status tab it shows the "Last execution" was this morning at 06:17, but the "Last trigger" shows 06:20:48. The timestamp for that record in my database is 06:20:48. I don't have anything configured on the "Trigger" tab. Since the beginning of the month, the timestamp in the database has been different times between 06:18:13 and 06:20:48. What I need help understanding is why, when executed at 06:17, does it not trigger and write to the database until at least a minute later. I'm sure there's a good explanation that I just need some help learning. Thanks in advance.
Hey @jkramer,
Are you able to provide a screenshot of the schedule configured for the Transaction Group, as well as the status page for the database connection used in the Transaction Group? It's also worth looking for long-running queries on the database connections status page of the gateway (Status > Connections > Databases) during the scheduled execution of the Transaction Group.
This would help isolate the issue a bit further. Normally the write to the database should be very close to the scheduled time (within milliseconds).
1 Like