- Release Notes
- Getting Started
- Setup and Configuration
- Automation Projects
- Dependencies
- Types of Workflows
- Control Flow
- File Comparison
- Automation Best Practices
- Source Control Integration
- Debugging
- Test Activities
- Debugging Actions
- The Locals Panel
- The Call Stack Panel
- The Breakpoints and Bookmarks Panel
- The Watch Panel
- The Immediate Panel
- Remote Debugging
- Profile Execution
- Logging
- The Diagnostic Tool
- Workflow Analyzer
- About Workflow Analyzer
- ST-NMG-001 - Variables Naming Convention
- ST-NMG-002 - Arguments Naming Convention
- ST-NMG-004 - Display Name Duplication
- ST-NMG-005 - Variable Overrides Variable
- ST-NMG-006 - Variable Overrides Argument
- ST-NMG-008 - Variable Length Exceeded
- ST-NMG-009 - Prefix Datatable Variables
- ST-NMG-011 - Prefix Datatable Arguments
- ST-NMG-012 - Argument Default Values
- ST-NMG-016 - Argument Length Exceeded
- ST-NMG-017 - Class name matches default namespace
- ST-DBP-002 - High Arguments Count
- ST-DBP-003 - Empty Catch Block
- ST-DBP-007 - Multiple Flowchart Layers
- ST-DPB-010 - Multiple instances of [Workflow] or [Test Case]
- ST-DBP-020 - Undefined Output Properties
- ST-DBP-021 - Hardcoded Timeout
- ST-DBP-023 - Empty Workflow
- ST-DBP-024 - Persistence Activity Check
- ST-DBP-025 - Variables Serialization Prerequisite
- ST-DBP-026 - Delay Activity Usage
- ST-DBP-027 - Persistence Best Practice
- ST-DBP-028 - Arguments Serialization Prerequisite
- ST-USG-005 - Hardcoded Activity Arguments
- ST-USG-009 - Unused Variables
- ST-USG-010 - Unused Dependencies
- ST-USG-014 - Package Restrictions
- ST-USG-020 - Minimum Log Messages
- ST-USG-024 - Unused Saved for Later
- ST-USG-025 - Saved Value Misuse
- ST-USG-026 - Activity Restrictions
- ST-USG-027 - Required Packages
- ST-USG-028 - Restrict Invoke File Templates
- ST-USG-032 - Required Tags
- ST-USG-034 - Automation Hub URL
- Variables
- Arguments
- Imported Namespaces
- Coded automations
- Introduction
- Registering custom services
- Before and After contexts
- Generating code
- Generating coded test case from manual test cases
- Trigger-based Attended Automation
- Recording
- UI Elements
- Selectors
- Object Repository
- Data Scraping
- Image and Text Automation
- Citrix Technologies Automation
- RDP Automation
- VMware Horizon Automation
- Salesforce Automation
- SAP Automation
- macOS UI Automation
- The ScreenScrapeJavaSupport Tool
- The WebDriver Protocol
- Extensions
- About extensions
- SetupExtensions tool
- UiPathRemoteRuntime.exe is not running in the remote session
- UiPath Remote Runtime blocks Citrix session from being closed
- UiPath Remote Runtime causes memory leak
- UiPath.UIAutomation.Activities package and UiPath Remote Runtime versions mismatch
- The required UiPath extension is not installed on the remote machine
- Screen resolution settings
- Group Policies
- Cannot communicate with the browser
- Chrome extension is removed automatically
- The extension may have been corrupted
- Check if the extension for Chrome is installed and enabled
- Check if ChromeNativeMessaging.exe is running
- Check if ComSpec variable is defined correctly
- Enable access to file URLs and Incognito mode
- Multiple browser profiles
- Group Policy conflict
- Known issues specific to MV3 extensions
- List of extensions for Chrome
- Chrome Extension on Mac
- Group Policies
- Cannot communicate with the browser
- Edge extension is removed automatically
- The extension may have been corrupted
- Check if the Extension for Microsoft Edge is installed and enabled
- Check if ChromeNativeMessaging.exe is running
- Check if ComSpec variable is defined correctly
- Enable access to file URLs and InPrivate mode
- Multiple browser profiles
- Group Policy conflict
- Known issues specific to MV3 extensions
- List of extensions for Edge
- Extension for Safari
- Extension for VMware Horizon
- Extension for Amazon WorkSpaces
- SAP Solution Manager plugin
- Excel Add-in
- Test Suite - Studio
- Troubleshooting
The Breakpoints and Bookmarks Panel
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 and Bookmarks panel.
|
Type |
Description |
|---|---|
|
Breakpoints |
Breakpoints pause the debugging process before the activity is executed. Breakpoints can have the following states:
|
|
Conditional Breakpoints |
Conditional breakpoints are breakpoints that depend on a set condition and/or a hit count. Conditional breakpoints can have the following states:
|
|
Tracepoints |
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:
|
|
Conditional Tracepoints |
Conditional tracepoints have a set condition or hit count, and a logged message. The message is logged when the condition is met the number of times stated in the hit count field. Conditional tracepoints can have the following states:
|
To modify the state of a breakpoint or tracepoint select the activity and press F9, click the icon in the Breakpoints and Bookmarks panel, or use the Designer or Breakpoints and Bookmarks panel context menus. You can also click the Breakpoints button on the Debug tab, open the drop-down menu and click Toggle Breakpoint.
Select a breakpoint in the panel and click the Delete button to remove it. The Delete all breakpoints option enables you to delete all the breakpoints in the current project. The Enable all breakpoints option helps you enable all breakpoints in the currently opened project. Consequently, the Disable all breakpoints option disables all breakpoints. Multiple selection is available in the Breakpoints and Bookmarks panel.
The Breakpoints and Bookmarks panel comes with a set of settings that can be
individually adjusted for each toggled breakpoint part of the automation project. Click the
icon to open the window.
The Breakpoint Settings window has the following options:
|
Option |
Description |
|---|---|
|
Condition |
The condition for the breakpoint. If the condition is met during debugging, the execution breaks and the activity is highlighted. |
|
Hit Count |
Specifies the number of times the condition must be met before the execution breaks. If the hit count is higher than the number of times the condition can be met, the execution does not stop upon encountering the breakpoint. The maximum hit count value is 32,767. |
|
Log Message |
Specifies the message to be logged at trace level when the condition is met. The message is visible in the Output panel. If a condition is not set, the message is still logged. |
|
Continue execution when logging |
If selected, the execution is not paused when the condition is met and the specified message is logged. Available only if a log message was previously set. |
Settings for any breakpoint in the project are visible upon hovering the breakpoint in the Designer panel.
Right-click an item in the Breakpoints and Bookmarks panel to open the context menu with the following options:
|
Option |
Description |
|---|---|
|
Delete |
Deletes the selected breakpoints. |
|
Focus |
Jumps to the breakpoint in the Designer panel. |
|
Enable |
Enables the selected breakpoints. |
|
Disable |
Disables the selected breakpoints. |
|
Settings |
Opens the Breakpoint Settings window for adding a condition to the breakpoint. |
Execution does not pause when a breakpoint is hit if the workflow contains:
- A UI Automation activity where any option is selected for the Wait for page load property.
- Two variables of different types that are called using the same expression.
Bookmarks enable you to mark and quickly jump to specific activities inside workflows. To place and modify a bookmark, simply right-click any activity and select Toggle Bookmark. This labels the activity with a bookmark [insert icon] icon.
You can filter between breakpoints and bookmarks in the panel by using the filter button. Similarly to breakpoints, selecting a bookmark in the panel and clicking the Delete button removes it from the project. The Delete all bookmarks options enables you to delete all the bookmarks in the current project. The Enable all bookmarks option helps you enable all bookmarks in the currently opened project. The Previous bookmark and Next bookmark options let you navigate between bookmarked activities.
| Option | Description |
|---|---|
|
Delete |
Deletes the selected bookmarks. |
|
Focus |
Jumps to the bookmark in the Designer panel. |
|
Enable |
Enables the selected bookmarks. |
|
Disable |
Disables the selected bookmarks. |
Deleting a bookmarked activity also deletes its corresponding bookmark. Similarly to breakpoints, bookmarks can be added during debugging.
The Breakpoints and Bookmarks panel displays all breakpoints and bookmarks in the current project, together with the file in which they are contained.
The Locations column shows the activity with the toggled breakpoint or bookmark, as well as conditions set to breakpoints.
The File Path column displays the file and its location.
For breakpoints, the Message column shows messages to be logged if the condition is met. Hover over the breakpoint tag on an activity to view its condition and log message. For bookmarks, the Message column lets you type messages that appear when hovering over the bookmark tag on an activity.
The Filter button hides or reveals the Breakpoints or Bookmarks sections in the panel.
Double-click on a breakpoint or bookmark to see the activity highlighted in the Designer panel. Use context menu options in the ribbon to enable or disable breakpoints or bookmarks.
To delete multiple breakpoints or bookmarks, select them and click Delete in the context menu. This removes the breakpoints or bookmarks from the current file.
The Delete all, Enable all and Disable all breakpoints or bookmarks buttons perform actions on all breakpoints or bookmarks listed in the panel, regardless if they are selected or not.
The Delete the selection button only deletes the selected elements. Deleting the Breakpoints or Bookmarks sections also deletes all breakpoints or bookmarks from the current file.
