Study guide

9.2 Agentic UI Automation: ScreenPlay, Semantic Activities & Healing Agent

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

9.2 Agentic UI Automation: ScreenPlay, Semantic Activities & Healing Agent

Key Takeaways Explain This Topic AI

ScreenPlay (formerly UI Agent, class UiPath.Semantic.Activities.NUITask) performs a UI task from a natural-language prompt and must sit inside Use Application/Browser.

ScreenPlay guardrails include Max number of steps, variable security against prompt injection, and trace attachment to jobs.

Semantic selectors act as a fallback or primary targeting method, and semantic activities (Fill Form, Extract Form Data, Update UI Element) handle forms by meaning.

Healing Agent gives recommendations and self-healing for UI Automation Modern activities in unattended, attended, and test runs, with Test Heals and RPA Heals tracked separately.

Healing Agent is enabled through AI Trust Layer governance and Orchestrator settings, and each activity has a Healing Agent mode.

Last updated: September 2026

9.2 Agentic UI Automation: ScreenPlay, Semantic Activities & Healing Agent

Core Concept: The January 2026 exam description adds "UiTask/UiAct — AGENTIC (healing scenarios, testing, attended scenarios)" under Advanced UI automation. UiPath's documentation does not define "UiAct" as a product name. What it documents is a family of agentic UI features : ScreenPlay (implemented as the activity class UiPath.Semantic.Activities.NUITask ), semantic activities and semantic selectors , and Healing Agent , which repairs failing UI automations. Learn what each one does, where it runs, and how it is governed.

ScreenPlay: Describe the Task, Let the Agent Act

ScreenPlay (earlier called UI Agent) is UiPath's agent for driving an application's interface from a natural-language instruction. It "interacts with applications much like a human would", navigating screens and adapting to changes instead of following fixed selectors.

Property What it does

Task The prompt describing the UI task. It can include variables, attached files, and images captured from the screen, and you can view the last execution trace.

Model The large action model that plans and reasons. UiPath offers several Screen Agent models with different speed, cost, and capability trade-offs.

Max number of steps A guardrail that caps how many actions the agent may take, which prevents endless agentic loops.

Job attachment mode When to attach the .html execution trace to the Orchestrator job: On failure, Always, or Never.

Use DOM when available Sends DOM data to UiPath's models where it can be extracted. Turn it off if DOM-based targeting leads to wrong coordinates.

Disable variable security Variable security stops prompt instructions from being injected through variable values; disable it only for a confirmed false positive.

Input mode The same choices as other UI activities: Same as App/Browser, Hardware Events, Chromium API, Simulate, or Window messages.

Key rules:

ScreenPlay must be placed inside a Use Application/Browser activity.

It is available in Windows and cross-platform projects, from the UIAutomation package versions that include it (UiPath's setup guide names 2025.10.20 or newer), with Studio connected to Automation Cloud.

It is governed through the AI Trust Layer , with protection against prompt injection.

UiPath's own advice is to keep workflows "maximally deterministic and minimally agentic" : use ordinary activities for predictable steps and ScreenPlay only where selectors are fragile or real reasoning is needed. ScreenPlay does not remember fallback paths between runs; each run reasons again from the current screen.

Semantic Selectors and Semantic Activities

These features apply AI to individual targets and forms, with tighter limits than ScreenPlay:

Semantic selectors use semantic understanding of the screen as a targeting method. They work as a fallback , triggered when traditional or Computer Vision targeting fails, or as a primary method for highly dynamic interfaces. UiPath bundles a monthly number of semantic selector runs with each platform tier.

Semantic activities handle forms: Fill Form , Extract Form Data , and Update UI Element (formerly Set Value). They match fields by meaning, which makes it easy to move data between web forms whose layouts differ.

UiPath calls these "micro agents": bounded, task-specific intelligence with predictable execution.

Healing Agent: Recovering Failing UI Automations

Healing Agent analyzes a UI automation just in time and chooses recovery strategies when it fails. It offers two benefits:

Recommendations. When a UI automation fails, it can suggest new selectors, smart delays, or code changes to handle unexpected pop-ups. These appear with the job in Orchestrator so a developer can update the workflow.

Self-healing. It complements Unified Target's own fallback by applying one or more recovery steps in a cascade, for example closing an overlay, adjusting a selector, and waiting for the page to load, so the job keeps running.

  • Scenario How Healing Agent helps
  • Unattended Background jobs on VMs that fail because of load times, unstable selectors, or pop-ups
  • Attended Automations running alongside a user, where user actions or UI changes break a step

Testing Healing during Test Manager and Test Cloud executions, counted as Test Heals and licensed separately from RPA Heals

Important details:

Healing Agent supports UI Automation Modern activities only , for desktop and web applications, and it can recover automations running in remote environments such as Citrix.

It is enabled through governance : an AI Trust Layer policy, plus settings at the Orchestrator process or job level. If self-healing is not activated, it only provides debug information and limited recommendations.

Individual activities have a Healing Agent mode property: Disabled , Inherit job settings , Recommendation only , or Same as App/Browser .

Choosing Among Them

Need Best fit

A stable, high-volume process with good selectors Ordinary Modern activities, with Healing Agent as a safety net

One field or element whose selector keeps drifting A semantic selector as a fallback or primary targeting method

Moving data between forms with different layouts Semantic activities such as Fill Form and Extract Form Data

A multi-step task in an application that changes often or has no usable selectors ScreenPlay, with a step limit and trace attachment

Test suites that break after UI releases Healing Agent during test executions (Test Heals)