I understand you can’t get the exception source unless an error is thrown inside an invoked workflow.
However I have noticed the information is held in $exceptionActivityInfo in the Locals panel during Debug mode.
Anyone know how to retrieve this?
This seems like the robot is not able to click on the URL tab with selector we have with that click activity
make sure that the selector is valid and enable the simulate click activity is enable in the property panel of click activity
–and also the click must be inside a ATTACH BROWSER activity and replace the selector having dynamic attribute value with wild cards like *
Hope this would help you
Thank you for responding so quickly, yes this was just a deliberately created scenario to create the failure and wasn’t expected to pass.
The issue as I understand it with UiPath at the moment is that it doesn’t allow you to see the Exception.Source unless the exception is thrown in an Invoked Workflow.
I was just wondering if there was a way of getting the contents of the $exceptionActivityInfo variable, so that I can record it for logging purposes to track down the source of any errors.
Using Exception.source just gives me UiPath.UiAutomation.Activities
I am using version 2019.4.2.
yah ofcourse thats possible
so keep all the activities inside the TRY block of TRY CATCH activity and if any error occurs it will go to CATCH block where we can get the source of the error and the error message as well like this with a log message activity
"Error occured at : "+ Exception.Source + " and due to : " Exception.Message
where in the catch block select the exception as
System.Exception which will include all the exception and gets us to catch block so that we can get the log message for recording
hope this would help you
I don’t think it works. I think the activity needs to be inside an invoked workflow in order for it to properly return the Exception.Source. I don’t really want to put my various sequence inside a workflow for this project.
It’s only showing UiPath.UiAutomation.Activities
I’m just wondering if there is a way to grab hold of the $exceptionActivitityInfo as shown in my original post. Which shows the source of the error.
From digging around, I’ve sort of narrowed down the number to be related to the .xaml structure. However, I don’t know how to extract it during actual run (only in debugging).
I’m keen to see if anyone else has a way of getting this as it would be super useful to pinpoint things with. There seems to be a improvement suggestion for something similar here: Activity Uid in case of application exception
and here: Component/Sequence/Workflow Name
Thank you AWoz - apologies for the late reply as I’ve been on holiday for the last week.
It would be good if the Guys/Girls from UiPath could make this variable available.
Again (to others reading this and UiPath) - the problem does go away if invoked workflows are used, however in some intances I am not using an invoked workflow and therefore can’t properly pinpoint the errors.
I just need that $exceptionActivityInfo available so I can log the details
I have a Global Handler where i log the “errorinfo.activityinfo” information. This provides activity name and instance ID (though still trying to figure out how to correlate Instance ID or ID with finding specific loading of activity in my code if it uses a generic name).
Did anyone found a fix for this ? I verified this as well and it seems the exception only shows the activity name when we extract the activity in a workflow and put that workflow in Try-Catch.
Then exception.Source shows the activity name which failed inside the Extracted Workflow.
I’ve given up on this and now ensure every sequence/activity I have is named which helps me track down any errors.
I suppose it’s good practice in a way :-S