Thanks for your response. Looks like the transaction got executed to certain extent(We have BLTH code to invoke 2 webservice calls for two different applications one after the another) and first webservice call to the first application is completed and post which it looks like an error is received during the second webservice call and then went to Audit state.
However, I was under the impression that all AUDIT transactions will never get processed as IM will reject them before processing. However, for this particular transaction it looks like here the transaction has been executed to certain extent(which I got a confirmation from the other application that they have received a webservice call from IM and I am not confirming this through IM logs) and then went to Audit State. Hence, I want to know if there will be any details in any of the logs that can show what has failed and why the transaction went to Audit state there after.
+1 214 923 2876
Classified - Confidential
Just to add, in VST I am not seeing any error. It is in AUDIT state and the error I see is a common error that comes for various other issues.
I would like you to try adding logging in the custom BLTH to trace out where the issue is. You can also add exception handling in the BLTH to return the error message to task screen.,
We had the same situation the task was moved to audited state when there is an failure in execution of BLTH.