Exception.Data is Null

Hi, I’m having a bit of a problem here and I don’t know what is happening.

I’m using REFramework, and the first activity inside my “Process.xaml” is a click which selector does not exist (this is intenteded, I’m forcing an error).
The error is then thrown back to the Catch of the “Process Transaction” State, inside the “Main.xaml” file.
But when inside this Catch, if I try printing the data from the error, this is what it appears.

Why are all those fields “null” inside the “exception.data” variable (please check the screenshot’s left panel)?, I need that info on my log, why is the Exception variable not being set?.

Hi @Axel_Albert

Place the breakpoint after assign activity and debug again.
Then assign variable execute and SystemException variable stores the data of the exception.

Please, consider paying attention to what I’m saying. And look to the left side, where I’m printing the “exception” variable not the “SystemException” one.

Hi @Axel_Albert ,

Could you maybe check on the below posts, i think it addresses the similar issues that you are facing :

No, it really doesn’t. I already know how to access that info, what I do not know, is why that info is “null” when I access it.
Please, check the screenshot, and the left panel where I’m showing the “exception.data” variable.

1 Like

yes exception.data is null. Im facing the same problem

Hi,

In assign activity, instead of Exception use Exception.Message

I’m sorry but why do people keep answering without paying attention to the actual problem and the actual thing that I’m trying to access?.

I do not desire the message, I desire all the rest of the info that UiPath is registering as “null”.
All that info was being registered and was accessible, and then since an update it was no longer being registered, but it’s still accessible (as null values).

Did you ever find out why the exception.data is null? It’s driving me nuts.

Best
Rickard

when the exception is thrown (e.g. from UiPath internal implementations) not in every case the Data Dictionary is populated (also the behaviour can differ on Activity, Package versions…)

So we would handle it defensive like:

  • Not isNothing(xx.Data) -checking it is populated
  • xx.Data.ContainsKey(“KeyName”) for testing on a partilclar key / xx.Data.Keys for getting all keys

and finally, we access as usual, when all constraints are met

About debugging we recommend to let the flow enter more into the modelling e.g. a breakpoint after the first activity from the modelling within the catch block. When too early setting the breakpoint we get nulls as not all from teh context is ready for us