I have a project that runs an MSSQL Execute action repeatedly as part of an iterated process. Most nights the process runs fine. Last night it failed on the 170th iterations, after 169 successes. The UPDATE statement that it was running was functionally no different from the previous 169, but on this one I got the following error in the log:
Executing Query: UPDATE crd_initiative SET hours_used = 5173.5 where initiative_id = 1000021
Is there any way to test for this, or keep it from happening? Should I set up retries on the Execute action? It seems very random, but it stops the whole process when it occurs. I don’t want to just “Ignore Failure”, because if one of the statements DOES fail I want to know about it.
Thanks,
Jonathan