Hello William, makes sense, but had already tried it. As mentioned it seems to happen in several places. In the example above Here is relevant code. (I have revised it to try a few things)
I tried several attempts in debug for it to highlight the correct offending code: the “Throw” statement . and I captured the debug log and local windows as well. (the local window is blank at this point. However, if you take a close log at the log output it is saying the “Throw” action failed to which, I am assuming, it generates the null reference exception. Why?
From what I can tell all information is populated correctly in the THROW properties. The strErrorMessage was used in a previous log statement that was displayed correctly in the log output, so why is the throw having an issue with a null reference? Is it because it is inside a catch block?
If that is the reason, I would have to try to find other failing code and see if this is too the reason, but as previously stated, tracking them down is not an easy task.