I have a project that is working fine and running as it should except for it seemed to be double logging to our SQL server.
I am looking into if this could be cause by somewhere inside of the perspective pages/scripting but I just wanted to make sure that my transaction groups aren't causing this for some weird reason.
Here are the settings for my transaction groups:
Any information is helpful!
First, make sure you did not create your transaction group in a project that is inheritable. If so, the transaction group will run in each child project that inherits from the parent.
2 Likes
Just checked and the project is not inheritable.
Maybe try with Reset trigger after execution
unselected. I think this setting is trying to reset the trigger tag to 0, but it's read only so it reverts to back to 1.
I tried that out and that doesn't seem to be the issue either. The value seems to reset the trigger correctly back to 0 when the "Reset trigger after execution". I tried turning it off and that value stays 1 and won't continue to log.
Another thing I am finding that is curious is all of the repeat logs are logged at the exact same time:
Not sure if this helps in anyway, but it makes me think that something weird is happening that is not script/Perspective related.. If it were script/perspective related, I would imagine the trigger would be turning on then off then on then off again, resulting in two logs at different times..
Go to the gateway → Status → Systems → Transaction Groups
and verify that you do not have multiple copies of the same group running.
Thought I checked that, but after double checking I think that was the issue. I had a backup copy of the program with active transaction groups.. I turned them off, saved, and will start to monitor the SQL data to make sure that was the issue.
Kicking myself for overlooking that... thanks for the help!!
1 Like
Can you mark the post as solved?
Just did, sorry about that