I would suggest you to try enclosing the sequence or module from where you want to check the error details (orgin-activity name, error description) within a try and catch. In the catch block by using,
Activity name where the error occured can be found by using, exception.source
The error description can be checked using,
exception.message / exception. Torstring.
Hope this helps.
Kindly Mark the answer as solution if it helps you.
Unfortunately, different versions behave slight differently around exception handling, and resent version doesnât return theses items in debug mode. So, perhaps you should check if itâs null or not, and also use Exception.Source etc.
(Probably, in actual run, it returns theses items)
Keep a breakpoint in your multiple assign activity in catch section. Then type exception.Data("FaultedDetails") expression in Immediate panel. It will give you the value if there is any info in Data property.
You can also try exception.Data("FaultedDetails").GetType().GetProperty("DisplayName").GetValue(exception.Data("FaultedDetails"),Nothing) expression in Immediate panel to check the result
I looked into various methods for fetching the activity name which is causing the exception.
I couldnât find anything as such , for the sake of finding the last activity before the exception we can open the orchestrator logs with log level set to trace which would help you to determine which activity caused the exception.
I understand the scenario is like, inside âApp_Login*â module you have the Try Catch Block and In main.xaml, it is being invoked.
Step 1 : Have the rethrow inside the catch block of âApp_Login*â module.
Step 2 : In the âMain.xamlâ, Enclose the âInvoke App_Login*â flow with Try catch, Have the invoke in the Try block and In the catch you can use âexception.Sourceâ and âexception.messageâ Just like in the earlier sample flow I had attached.
Attaching one more flow for your reference, TestProcess.zip (4.4 KB)
Hope this helps you. CheersâŚ!!
Happy AutomatingâŚ!!