How to get Exception source "Activity Description name"


How to get the exception source highlighted in the below mentioned screenshot, in catch block to identify in which UIPath activity throwing the exception.


1 Like

Hey @siva

You can get the source by using “exception.source”.

please find below screenshot:


1 Like

exception.Source not giving the “Activity Description Name”, it always showing “System.Data”.


Please check the post below and check if it helps

Sachin Desai


Thank you so much, This works fine :slight_smile:

That is the same thing. why not working earlier?

hey its not working for me
It shows only UiPath.core.Activities

1 Like

Any solution you got for the issue? Even i am facing similar issue.

Hello Folks,

I guess we need activity description in exception for detailed logging. It seems till now only we can get workflow names not the activity names under catch using exception.source.

Here is an approach, kind of simple. Create Main level variable (Ex. ActivityTracker), update this variable where you are doing application level interactions.
Keep couple of things in mind:

  • Update this variable before the activity
  • This approach can be used either as practice to whole process or not
    Example is attached. (4.4 KB)

Consider this example is to show error handling, so simple step is failing and you can see activity name is tracked in Catch block.
If you want to remove that error, in selector change from aaname=‘Sezarch’ to aaname=‘Search’

The issue is strange. What @Sachin_Desai has mentioned worked when the exception is in different workflow.
But if the exception is in same workflow where the Try-catch block is, then exception.Source shows something like “UiPath.Core.Activities” instead of showing the activity description.

This is strange.

This is in fact happening. Is there any solution other than using invoke inside Try Catch?

Guys, this bug is serious and annoying. Can anyone help or confirm this behaviour ?

Please find attached a pratical example: (20.2 KB)

Thank you.

I had faced this problem, handled this in a different way, for every screen I have created 2 workflows, parent & child, in the parent work flow I have put try/catch, very little & error free code, in the child workflow write the entire logic. This way it is showing me the exact error source.

1 Like

Another option is just create a variable strSource and assign a meaningful activity name as string before the actual activity. But these are very cumbersome process.

UiPath should resolve this bug. @ovi and @Sachin_Desai must take a look at it.


Hi Joasantos, same issue here. For now the only solution is to remove the trycacth (or use a rethrow) to let the studio outline the activity that was in error …

I agree @amakundu.