- Release Notes
- Getting Started
- Setup and Configuration
- Automation Projects
- Dependencies
- Types of Workflows
- File Comparison
- Automation Best Practices
- Source Control Integration
- Debugging
- 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-DBP-002 - High Arguments Count
- ST-DBP-003 - Empty Catch Block
- ST-DBP-007 - Multiple Flowchart Layers
- ST-DBP-020 - Undefined Output Properties
- 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
- Recording
- UI Elements
- Control Flow
- Selectors
- Object Repository
- Data Scraping
- Image and Text Automation
- Automating Citrix Technologies
- RDP Automation
- Salesforce Automation
- SAP Automation
- VMware Horizon Automation
- Logging
- The ScreenScrapeJavaSupport Tool
- The WebDriver Protocol
- Test Suite - Studio
- Extensions
- Troubleshooting
- About troubleshooting
- Microsoft App-V support and limitations
- Internet Explorer X64 troubleshooting
- Microsoft Office issues
- Identifying UI elements in PDF with Accessibility options
- Repairing Active Accessibility support
- Automating Applications Running Under a Different Windows User
- Validation of large Windows-legacy projects takes longer than expected
About Debugging
Debugging is the process of identifying and removing errors that prevent the project from functioning correctly. It is recommended to perform debugging during the design stage of the automation project, at activity, file and project level.
Debugging can be performed using several options, defined in the ribbon and explained in the Debugging Actions page.
By default, debugging is performed on the local robot. You can run or debug your projects using a robot on a remote machine by enabling remote debugging.
Several panels make it easier to view the debugging process, add values or monitor variables and arguments.
The options for running and debugging a file or project are available both in the Design and Debug tabs.
|
Option |
Description |
|---|---|
|
Debug |
Click Debug or use F5 to debug the whole project. |
|
Run |
Click Run or use Ctrl + F5 to run the whole project. |
|
Debug File |
Click Debug File or use F6 to debug the current file. |
|
Run File |
Click Run File or use Ctrl + F6 to run the current file. |
The default action under Run/Debug ribbon button can be configured from Backstage View > Settings > Design tab. Pick from Debug File, Run File, Debug Project, or Run Project, as the default action when clicking the button.
During debug, click the Break button to pause. The activity which is being debugged remains highlighted when paused. Once this happens, you can choose other debug actions like Step Into or press Stop to exit and return to design mode. The keyboard shortcut for the Stop button is F12.
It is recommended to use Break along with Slow Step so that you know exactly when debugging needs to be paused.
The Continue option is available when the debug process is paused.
