robot
latest
false
- Getting started
- Understanding UiPath Robot
- Installation requirements
- Installing robots for unattended automations
- Configuring robots for unattended automations
- Deploying unattended automations
- Connecting robots for unattended automations to Orchestrator
- Setting up Windows Server for High-Density Robots
- Redirecting robots through a proxy server
- Implementing authentication with credential providers
- Configuring package signature verification
- Setting up package folders and network paths
- Configuring activity feeds
- Using EntraID users with multifactor authentication (MFA) for unattended robots
- Installing robots for attended automations
- Configuring robots for attended automations
- Integrations
- Governance
- Troubleshooting
- Log levels
- Log fields
- Log storage
- Managing robot logs
- Stack trace details
- Robot Service troubleshooting
- Execution troubleshooting
- Recording and Remote Control troubleshooting
- Networking troubleshooting
- Connection troubleshooting
- Licensing troubleshooting
- Package troubleshooting
- .NET troubleshooting
- Logging troubleshooting
- Session troubleshooting
Robot admin guide
Last updated Mar 3, 2026
Stack trace details
Runtime errors provide a human-readable stack trace to help you locate the activity that caused your workflow execution to fail. This stack trace is visible at runtime in Studio, Orchestrator, and in Robot logs.
It contains the workflow file name, activities name, and execution hierarchy, as follows:
- Source: The activity that caused the error.
- Message: The error message.
- Exception type: The specific type of the exception thrown.
- A stack trace showing the path from the main workflow down to the activity that generated the error. For the example in the image, the hierarchy is: Main > Main Sequence > Sequence1 > Activity1 > Sequenc > Sequence3 > Parallel3 > Throw.