Study guide
15.2 Remote Debugging: Remote Machine and Unattended Robot Connections
UiPath Automation Developer Professional UiPath-ADPv1
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Exam Overview & Blueprint Map
1.1 About the UiPath-ADPv1 Exam: Format, Fees & Policies 1.2 The Exam Topics Mapped to This Guide & a Study Plan
2 Chapter 2: REFramework Architecture & State Dynamics
2.1 State Machine Architecture & The Four Core States 2.2 Configuration Management: Settings, Constants, and Assets 2.3 Transaction Types & The Dispatcher vs. Performer Architecture 2.4 Adapting REFramework: Tabular Data, Collections & Linear Processes
3 Chapter 3: REFramework Exception Handling & Recovery
3.1 BusinessRuleException vs. System.Exception Handling Patterns 3.2 Retry Mechanisms: Queue Retries vs. REFramework MaxRetryNumber 3.3 Consecutive System Exceptions & Graceful Process Termination
4 Chapter 4: State Machines, Custom Log Fields & REFramework Testing
4.1 Building State Machine Projects in Studio 4.2 Logging Levels, Robot Logs & Custom Log Fields in REFramework 4.3 Testing a REFramework Project With and Without Orchestrator Queues
5 Chapter 5: LINQ Queries & DataTable Operations
5.1 LINQ Essentials for Collections & Filtering 5.2 Advanced DataTable Querying with LINQ 5.3 In-Memory DataTable Transformations & Column Operations
6 Chapter 6: Regex, DateTime, JSON & Invoke Activities
6.1 Regular Expressions & Text Parsing for Automation 6.2 DateTime Formatting, Timezone Conversions & TimeSpan Calculations 6.3 JSON Parsing, JSONPath & Serialization with Newtonsoft.Json 6.4 Invoke Method & Invoke Code Activities 6.5 Data Referencing in Invokes: DataTable, List & Dictionary Arguments
7 Chapter 7: Modern UI Automation & Unified Targeting
7.1 Modern Design Experience & The Unified Target Concept 7.2 Anchors, Relative Elements & UI Automation Activities 7.3 Dynamic Selectors, Variables & Wildcards in Selectors
8 Chapter 8: Object Repository, Computer Vision & Remote Runtime
8.1 Object Repository & UI Descriptor Libraries 8.2 AI Computer Vision for Unattended & Remote Interfaces 8.3 Automation in Virtual Environments & UiPath Remote Runtime
9 Chapter 9: Advanced UI Automation: Browser Modes, Agentic UI & macOS
9.1 Browser Automation with the WebDriver Protocol 9.2 Agentic UI Automation: ScreenPlay, Semantic Activities & Healing Agent 9.3 macOS Automation: Native Apps, Office Apps & AppleScript
10 Chapter 10: Advanced Control Flow & Exception Architecture
10.1 Flowcharts, Sequences & Parallel Control Flow Patterns 10.2 Global Exception Handler Architecture & ErrorAction Directives 10.3 TryCatch, Retry Scope & Custom Exception Architectures
11 Chapter 11: Orchestrator Queues & Transaction Management
11.1 Queue Architecture, SpecificContent & Transaction Lifecycles 11.2 Queue Items SLA, Postpone, Deadlines & Priority Scheduling 11.3 Bulk Operations, Transaction Status Updates & Queue Triggers
12 Chapter 12: Orchestrator Tenant & Folder Entities
12.1 Asset Types, Per-Robot Assets & External Credential Stores 12.2 Modern Folder Hierarchy, User/Robot Assignment & Permissions 12.3 Storage Buckets, Webhooks & Environment Promotion 12.4 Orchestrator Tags: Labels, Properties & Governance
13 Chapter 13: Unattended Execution, API Triggers & Cloud Robots
13.1 Unattended Job Execution: Folders, Priorities, Background vs. Foreground & Runtimes 13.2 API Triggers: Starting Jobs from External Systems over HTTP 13.3 Serverless and Cloud VM Robots: Cloud-Hosted Execution Options
14 Chapter 14: Monitoring, Recording & Solutions Management
14.1 Orchestrator Monitoring, Trigger Alerts & Job Health 14.2 Job and Transaction Recording: Troubleshooting Faulted Unattended Jobs 14.3 Solutions Management: Packaging and Deploying Automations with Their Resources
15 Chapter 15: Debugging, Remote Debugging & Profiling
15.1 Studio Debugging Tools: Breakpoints, Panels & Execution Control 15.2 Remote Debugging: Remote Machine and Unattended Robot Connections 15.3 Profile Execution: Finding Performance Bottlenecks in Studio
16 Chapter 16: RPA Testing & Test Suite
16.1 UiPath Test Suite Overview, Test Cases & Given-When-Then Structure 16.2 Data-Driven Testing, Test Verification Activities & Mock Activities 16.3 CI/CD Pipelines with uipcli & Test Manager Traceability
17 Chapter 17: Long-Running Workflows, Action Center & Apps
17.1 Long-Running Workflows: Persistence, Suspend and Resume 17.2 Action Center & Human-in-the-Loop Orchestration 17.3 UiPath Apps: Action Apps, Automations & Integration Service
18 Chapter 18: Trigger-Based Attended Automation & Callouts
18.1 Trigger-Based Attended Automation: Forms, Triggers & Global Variables 18.2 Running Local Triggers & the Event Inspection Tool 18.3 Callouts & Forms for Attended Guidance
19 Chapter 19: UiPath Assistant & Robot Sessions
19.1 UiPath Assistant: Automations, Reminders, Widgets & Configuration 19.2 Robot Session (Picture in Picture): Child Session vs. Virtual Desktop
20 Chapter 20: Autopilot for Developers & Autopilot for Everyone
20.1 Autopilot for Developers: AI Assistance in Studio and Studio Web 20.2 Autopilot for Everyone: Chat, Automations & Clipboard AI
21 Chapter 21: API Automation & Integration Service
21.1 Integration Service: Connectors, Connections & Connector Activities 21.2 API Workflows in Studio Web 21.3 HTTP Requests: Web APIs, the Orchestrator API & Connector Requests 21.4 Connector Builder: Custom Integration Service Connectors 21.5 Integration Service Event Triggers: Connected and Disconnected 21.6 GenAI Activities: Generative AI Inside Workflows
22 Chapter 22: Data Service, Context Grounding & Coded Workflows
22.1 Data Fabric (Data Service) Entities: Modeling Business Data 22.2 Data Fabric Activities and the Platform Connector 22.3 Context Grounding: Retrieval-Augmented Generation with Company Data 22.4 Coded Automations: Structure, Arguments & Invoking Workflows 22.5 Coded Automation Services: Orchestrator, UI Automation, Microsoft 365 & Custom Services
23 Chapter 23: Integrated Scenario Practice
23.1 Integrated Scenario Practice: Designing an End-to-End Solution
15.2 Remote Debugging: Remote Machine and Unattended Robot Connections
Key Takeaways Explain This Topic AI
Remote debugging runs and debugs the open Studio project on a robot on another machine, for attended and unattended processes, including Linux robots.
Remote Machine connections use TCP/IP to the UiPath.RemoteDebugging.Agent (default port 8573, optional password); the robot must match the Studio version.
Unattended Robot connections go through Orchestrator 2021.10+ in the same tenant and need job and storage permissions plus an Unattended, NonProduction, or Testing runtime.
When the Remote Debugging button is highlighted, all run and debug operations execute remotely, and the status bar turns green.
Coded automations cannot be remote debugged, and long-running workflows require an Unattended Robot connection.
Last updated: September 2026
15.2 Remote Debugging: Remote Machine and Unattended Robot Connections
Core Concept: Automations can behave differently on the production machine than on the developer's PC, because of different hardware, software, permissions, or an isolated network. Remote debugging runs and debugs the open Studio project on a robot on another machine, with the same stepping, breakpoints, and panels as local debugging. It works for attended and unattended processes, including cross-platform projects on Linux robots.
Two Connection Types
Remote Machine Unattended Robot
How Studio connects Direct TCP/IP connection to the robot on the remote machine Through Orchestrator , to an unattended robot in the same tenant
Set up on the robot side Run the UiPath.RemoteDebugging.Agent utility to accept requests None beyond a configured unattended robot
Versions Remote robot is the same version as Studio ; compatible .NET installed Studio, robot, and Orchestrator 2021.10 or later ; robot the same version as Studio
Packages Studio sends the dependency list and its activity feeds ; the robot downloads from those feeds Studio sends only the dependency list; the robot uses the Orchestrator feeds and its own feeds
- Extras Password-protected agent port Show Live Stream and remote control of the robot session
- Remote Machine Connection
- Configure the robot machine
On a Windows robot, open a command prompt in the Studio or Robot installation folder (by default %PROGRAMFILES%\UiPath\Studio per machine) and run: UiPath.RemoteDebugging.Agent.exe enable --port <port_number> --password <password> --verbose
All arguments are optional. Without --port , the agent uses port 8573 , which must be open in the firewall and not used by another application.
--password sets a password that Studio must supply.
Linux and macOS robots run the same agent with dotnet UiPath.RemoteDebugging.Agent.dll enable ... .
The agent confirms: "Robot on machine hostname is waiting for remote debugging instructions on port port_number".
While the robot is in remote debugging state, no attended or unattended jobs can run on it from Orchestrator or the local Assistant. Remote debugging commands can be sent even to robots whose installation is not licensed.
If Orchestrator enforces interactive authentication and you debug an unattended process, the robot must be signed in interactively, have a user signed in through Assistant, or have a troubleshooting session enabled in Orchestrator for the machine.
Configure Studio
On the Debug tab, open the arrow under Remote Debugging and select the settings option.
Set Connection Type to Remote Machine .
Enter Host , Port (default 8573), and Password , optionally select Test Connection , and Save .
- Unattended Robot Connection
- Prerequisites
Studio and the robot are connected to the same Orchestrator tenant.
The Studio user can start jobs and create and delete storage buckets and storage files in the folder; the robot account can view storage buckets and storage files.
The machine has an Unattended , NonProduction , or Testing runtime available.
For foreground processes, Run foreground automations is enabled for the robot in Orchestrator.
Configure Studio
Set Connection Type to Unattended Robot . Save to use any available connected machine in the folder selected in the Studio status bar, or choose User , Machine , and Hostname . Show Live Stream opens a window showing the robot's actions, where you can also take remote control without pausing the automation.
Live streaming is supported for Automation Cloud and Automation Suite Orchestrator, needs the robot service in service mode, and needs a VNC server on Windows robots; serverless cloud robots need no extra setup. When debugging with a serverless robot, Orchestrator's automatic machine size for remote debugging jobs is Medium.
Switching Between Remote and Local Execution
Once a connection exists, the Remote Debugging button toggles remote execution:
Highlighted in gray: every run and debug operation (Debug File, Run File, Debug Project, Run Project, Step Into/Over/Out, Test Activity, Run to/from this Activity) runs on the remote robot. The Studio status bar turns green during remote execution.
Not highlighted: operations run on the local robot.
To close the connection, set Connection Type to Disabled when nothing is running.
Limitations to Remember
Coded automations cannot be remote debugged.
Long-running workflows can be remote debugged only with an unattended robot connection.
With an unattended robot connection, the Picture in Picture option does not start a separate session.
On a remote machine connection, a long pause can end in a Connection Closed error in Studio; increase the TCP idle timeout on the load balancer if needed.
The project must be open in Studio. With source control, UiPath recommends Enforce Check-In before Publish so you debug the latest version.
Choosing a Connection
- Situation Choose
- Robot in an isolated lab network reachable from the developer PC Remote Machine
- Unattended cloud or server robot managed by Orchestrator, no inbound ports allowed Unattended Robot
- Need to watch the robot's screen while debugging Unattended Robot with Show Live Stream
- Debugging a long-running process that suspends and resumes Unattended Robot
- Project is a coded automation Neither; debug locally