How to make let the robot not stop at the throw activity in debug mode

Learning & Development Programs Reboot Your Skills 2021
1

Hi all,

When I run my robot in debug mode it stops at the throw activity. Is it possible to make sure it does not do that, or at least continue with the next transaction instead of stepping out of every activity the throw activity is in.

Thank you,

Oscar

2 Likes
2

Hello

In studio, the default “Run” option (the big blue arrow) is debug.

If you click the text “Debug File” then select “Run file” that should continue without stopping.

image

I hope this helps.

Cheers

Steve

3 Likes
3

Thank you for your response, the problem is that I do want the robot to stop at breakpoints, just not when a transaction item is thrown.

Thanks,

Oscar

4

Hello

At the throw activity (I think) there is an option to not stop the workflow.

Let me know how you go :slight_smile:

5

Hi, sorry for the late replay,

In the debug mode there is the option of not stopping at exceptions, however this also makes it not stopping at errors, while I am trying to only continue when there is a throw.

Best wishes,

Oscar

6

I’m facing the same. There is no option to avoid stop on the Throw activities and need to manually click the run/step out button literally 5-7 times to just come out of throw. Wondering there is no resolution on this becasue this consumes a lot of time during debug and testing.

7

On the debug tab, click the button to turn on “continue on exception”

image

2 Likes
8

Oh thank you so much this resolved the problem. This is a big time saver for testing.

Any idea how to step out and come out of whole xaml file? Currently step out only comes out of current container so that also requires multiple clicks to come ouf of a Invoke xaml.
Or they should add another Step out which completes the whole current xaml and stops at the main calling page.

Any idea if I’m doing it the wrong way or any solution for this. Again manually adding breakpoint can resolve this but want to avoid that too so any advise…

9

This button cant be enabled or disabled during the debug. For complex automation this again cosumes more time if you forgot to enable or disable this button because you need t o again reset process change this button and re-run. I think there can be a better approach here to reduce the testing time.