Question 21

Explanation

Breakpoints are used to purposely pause the debugging process on an activity which may trigger execution issues. Setting a condition and/or hit count turns the simple breakpoint to a conditional one. Adding logging results turns the conditional breakpoint in a conditional tracepoint. Adding only a logging message transforms the breakpoint to a simple tracepoint.

You can place and modify a breakpoint on any activity as follows:

• from the context menu, right-click an activity and select Toggle Breakpoint;

• by selecting the activity, and clicking the Breakpoints button on the Debug tab;

• by pressing F9 while the desired activity is selected.

A single activity needs to be selected for a breakpoint to be toggled. You can, however, toggle as many breakpoints as you see fit. Make sure that the order of activities in the workflow is not changed after the breakpoint is set.

Each breakpoint or tracepoint receives a specific icon based on its state. The icon is set on the activity and visible in the Breakpoints panel.

Tracepoints are breakpoints with set logged messages. When the tracepoint is reached during debugging, the message is logged at trace level. Tracepoints can have the following states:

https://docs.uipath.com/studio/docs/the-breakpoints-panel

Debugging Features

What it is and why you need it

What it is

Let's have a quick look at the new debugging features:

• The Debug File or Debug Project, Run File or Run Project options are now states of the same button in the ribbon.

• The Locals panel shows the values for arguments, the properties of the current and those of the previously executed activity. The values of variables and arguments can be modified from this panel. The design of the panel has been improved.

• You can right click variables or arguments in the Locals panel to add them to the Watch panel.

• Details about the thrown exception are displayed in the Locals panel.

• The Immediate panel lets you evaluate expressions you define during debugging to inspect data.

• You can monitor the execution of activities, containers and project files by using the Call Stack panel. This panel allows for easy access to the activity which threw an exception.

• When working with breakpoints, you can now add conditions, a hit count and log a message when hit.

• Activities can now be tested either inside the workflow using the Test Activity context menu option, or from the Activities panel by creating a test bench.

• Run to this Activity and Run from this Activity context menu options start debugging the workflow to and from a certain activity.

• Use the Restart ribbon option to restart the debugging process from the first activity in the process or the activity from which the Run from this Activity option was triggered.

• The new Step Out action finishes the execution of the current activity and returns to the level of the container, pausing the debugging process.

• Whenever an exception is encountered during debugging, you can Break, Ignore the error and Continue. The Retry option re-executes the previous activity, and throws the exception if it's encountered again. These actions are now available in the Debug tab.

https://docs.uipath.com/studio/docs/about-debugging

Why you need it

The new approach will make it easier for you to build reliable workflows faster.

The Debugging actions and panels

UiPath is continuously improving an integrated debugging experience.

Debugging actions

https://docs.uipath.com/studio/docs/debugging-actions