Workflow

replied on March 15, 2021

When viewing the Workflow history, you should be able to see the error that triggered the try-catch block on the "Messages" tab. Is that not working in your case?

Some errors will show on the Windows Event Viewer on the server running LFWorkflow - but having a try-catch block is intended to catch the error and handle it, so it probably won't get to those logs.

The Workflow Administration Console keeps error logs too. I checked one of mine that I know always hits the Try-Catch block (it is populating a very large form and thinks it Times Out when it actually succeeds). Not only do I see the error on the "Messages" tab on the Workflow history, but I also see the error on the "activity errors.log" file from the Workflow Administration Console.

1 0

replied on March 15, 2021

Thanks for the response but I am looking for close enough option of debugging a workflow and want to check token values within foreach loop which is within try catch block

0 0

replied on March 15, 2021 • Show version history

Your best best for token values is the Track Tokens activity - you can specify which token(s) you want to track, and can use it multiple places if you need to track how your token changes as the Workflow processes. You can use it in your loop and it will track the token(s) at each iteration of the loop.

0 0

Question

Question

Replies

Sign in to reply to this post.