- 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
- Citrix Technologies Automation
- 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
Profile Execution
When you run or debug a workflow, Profile Execution provides a performance analysis of all the operations, showing you a cumulative percentage of the execution time of each activity.
- Profiling data generated during debugging might be different from data generated during production (running the file).
- The data is stored for each session in
C:\Users\username\AppData\Local\UiPath\ProfiledRuns(see Import previous profiling sessions).
To profile an execution, run a file or debug the file, then go to the Debug ribbon tab.
Make sure that your automation works correctly without slow performing workflows. If you identify potential flow issues, you can review workflows that take longer to be completed. Use the context menu for profiling to take actions.
The Execution Details at the bottom of the Profiling tab shows the number of executions and descriptive statistics such as the average duration and the minimum and maximum duration values.
You can import profiling sessions to examine previous runs. Focus is disabled on imported profiling sessions.
|
Action |
Description |
|---|---|
|
Open |
Right-click the parent file in the Profiling tab and select Open to jump to the selected workflow. |
|
Focus |
Right-click an activity and select Focus to center the Designer panel view on the selected activity. |
|
Search |
Use the search function to look for specific activities. |
|
Expand/Collapse All |
Use Expand All and Collapse All to bring to view or collapse all activities. |
