Study guide
19.2 Robot Session (Picture in Picture): Child Session vs. Virtual Desktop
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
19.2 Robot Session (Picture in Picture): Child Session vs. Virtual Desktop
Key Takeaways Explain This Topic AI
A Robot session (previously Picture in Picture) isolates an attended automation from the user's work.
Child Session (PiP Type New Session) supports hardware events and image automation; Virtual Desktop (New Desktop) is faster and lighter but supports neither.
Child Session PiP is enabled with UiRobot.exe PiP --Enable as administrator, or ENABLE_PIP=1 at installation, and is unavailable on Home editions of Windows 8 and 10.
PiP Options record whether a project was tested for PiP and whether it starts there by default.
Invoked workflows can target the Current, Process Default, Main, or Picture in Picture session.
Last updated: September 2026
19.2 Robot Session (Picture in Picture): Child Session vs. Virtual Desktop
Core Concept: A Robot session , previously called Picture in Picture (PiP) , runs an attended automation isolated from the user's own work, so both can use the machine at once. There are two technologies: Child Session and Virtual Desktop .
The Two Technologies
- Child Session Virtual Desktop
- How it isolates A separate Windows session on the machine The same Windows session , on a virtual desktop
- PiP Type setting New Session New Desktop
Start time and resources Slower to start; keeping one open all day gives similar performance Faster and uses fewer resources
- Hardware events UI automation Supported Not supported
- Image-based automation Supported Not supported
- Simulate and Windows Messages input Supported Supported (not every application supports these methods)
- Edge and Chrome automation Supported Supported with UIAutomation Activities 22.4 or later
- Windows editions Not available on Home editions of Windows 8 and 10 Runs on more Windows versions
UiPath's guidance: Child Session suits complex automations that need hardware events and image-based automation, while Virtual Desktop is recommended when both work, because it is faster and lighter.
Enabling Child Session PiP
Child Session PiP must be enabled on the machine:
On an existing installation, run UiRobot.exe PiP --Enable (or --Disable ) with administrator rights ; the setting affects all users of the machine.
During a command-line installation, pass ENABLE_PIP=1 to the installer.
Things to remember about Child Session:
You cannot restart or shut down the machine while the Robot session is active.
The clipboard is shared between the Robot session and the main session.
PIN and smart-card sign-in work only the first time a session is spawned; after that, the session is authenticated with username and password until the machine restarts.
Configuring Processes for a Robot Session
In Studio's Project Settings , the PiP Options record whether the project was tested in a Robot session and whether it starts there by default:
- PiP Options value Effect when run
- Tested for PiP usage; Starting in PiP Starts in a Robot session by default
- Tested for PiP usage; Not starting in PiP by default Starts in the main session, but can be run in PiP
- Not tested for PiP usage Starts in the main session; running it in PiP asks the user to confirm
PiP Type chooses New Session (child session) or New Desktop (virtual desktop).
In Studio, the Picture in Picture option on the Debug tab runs or debugs the process in a separate session or virtual desktop so you can test it before setting these options.
Choosing Where Invoked Workflows Run
Invoke Workflow File can choose a target session for the invoked workflow:
- Target session Meaning
- Current The same session as the parent
- Process Default The session set in the invoked process's settings
- Main The user's main session
- Picture in Picture The Robot session
A common design runs the background-safe parts in the Robot session and switches to Main for steps that must interact with the user's session, such as a message to the user or an application that cannot run twice.
Design Tips
Choose input methods that work in both technologies. Prefer Simulate , or Windows Messages where the application supports it. Avoid hardware events if the process must run in a Virtual Desktop.
Avoid image-based steps if you want Virtual Desktop.
Watch shared resources. Both sessions share the clipboard and some applications allow only one instance per user; design around this, for example by not using copy and paste to move data.
Test with PiP on in Studio before marking the project as tested.
Testing Checklist Before Marking a Project as Tested for PiP
Run the process in Studio with the Picture in Picture option on the Debug tab, using the PiP Type you intend to publish.
Confirm every UI step works with the chosen input methods.
Check steps that use the clipboard or single-instance applications while the user is working in the main session.
Only then set PiP Options to one of the "Tested for PiP usage" values and publish.
Worked Example
An HR onboarding automation fills forms in a web HR system and a desktop payroll client.
The web steps use Simulate input and work in both technologies.
One payroll screen only responds to hardware events, so the team chooses Child Session (PiP Type New Session ), enables PiP on the machines with UiRobot.exe PiP --Enable , and marks the project Tested for PiP usage; Starting in PiP .
A final confirmation dialog is invoked with target session Main so the HR specialist sees it in their own session.
Common Traps
Virtual Desktop does not support hardware events or image-based automation.
Child Session is not available on Home editions of Windows 8 and 10 and needs PiP enabled with administrator rights.
"Not tested for PiP usage" does not block PiP; it asks the user to confirm.