Study guide

14.2 Job and Transaction Recording: Troubleshooting Faulted Unattended Jobs

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

14.2 Job and Transaction Recording: Troubleshooting Faulted Unattended Jobs

Key Takeaways Explain This Topic AI

Recording is a process setting on the Additional settings tab, disabled by default, and applies only to unattended automations.

Video captures the last 3 minutes, with options for failed jobs only, failed queue transactions, or all jobs.

Queue transaction recording requires the queue activities; status changes through HTTP or external APIs are not recorded.

Videos are kept 7 days (failed) and 3 days (successful) on Community, 14 and 7 days on Enterprise; screenshots are kept 30 days.

The Execution Media permission (View, Create, Delete) controls recordings, and recording activity is audited.

Last updated: September 2026

14.2 Job and Transaction Recording: Troubleshooting Faulted Unattended Jobs

Core Concept: Orchestrator can record the last moments of unattended executions as video or screenshots , so developers can see what happened on the robot's screen when a job or queue transaction failed. The exam description lists "Unattended automations features: recording".

Where to Enable Recording

Recording is configured per process , when you create it or later from the process settings. The Job Recording option is on the Additional settings tab and is disabled by default . The feature applies only to unattended automations .

Video Recording

Video captures the last 3 minutes of the execution. When enabled, choose one of these settings:

Setting What is recorded Availability

Record and store only failed jobs Only executions that fail Automation Cloud Robots - Serverless, or Robot 2023.2 or later

Record and store failed queue transactions Executions with failed queue transactions; the recording is shown with the transaction Serverless, or Robot 2023.10 or later with System Activities 2023.10 or later; the process must use queues

Record all jobs Every execution Serverless, or Robot 2023.2 or later

UiPath recommends turning on Record all jobs only briefly, to observe odd behavior, and then switching to failed-only recording to save bandwidth and storage.

Details that matter

Queue transaction recording works only when the item status is changed with the dedicated queue activities , such as Set Transaction Status. Status changes made through HTTP activities or external API calls are not recorded.

When a job is suspended and later resumed , the video includes only the execution after the resume.

Viewing a recording

From the job's details, using Open recording , or the job's context menu.

On the Video timeline tab, where logs are synchronized with the video: select a log entry to jump to that moment, filter logs by severity, and download the logs and the video.

For a failed queue transaction, from the transaction's context menu or its details window.

How long videos are kept

  • Plan Failed jobs and failed queue transactions Successful jobs
  • Community 7 days 3 days
  • Enterprise 14 days 7 days

After that, videos are no longer available in Orchestrator; download any video you need to keep.

Screenshot Recording

Screenshots of the last moments before a failure are the lighter alternative:

  • Setting Meaning Limits and default
  • Scaling Screenshot scale in percent Maximum 100; default 100
  • Frequency Interval between screenshots, in milliseconds Minimum 250; default 500
  • Duration Seconds before the failure to capture Maximum 120; default 40

Screenshots are retained for 30 days . The screenshot option does not work with Robots older than 2019.3 or with Cloud Robots - Serverless.

Permissions: Execution Media

Recording is controlled by the folder-level Execution Media permission:

  • Permission Allows
  • View Watching and downloading recordings, including the Download option on the Jobs page
  • Create The account that runs the job can create the recording
  • Delete Deleting recordings

The default folder roles that include Create on Execution Media are Folder Administrator , Automation User , and Robot . Video recording activity is included in the Orchestrator audit .

Recording Versus Other Diagnostics

  • Tool Best for Limitation
  • Video recording Seeing the UI state that led to a failure Last 3 minutes only; limited retention
  • Screenshots A light record of the last seconds Up to 120 seconds before failure

REFramework exception screenshot A single image at the moment of a System Exception Only what the template captures, saved on the robot machine

  • Logs The sequence of activities, values, and errors No visual context
  • Healing Agent Recommendations or self-healing for UI targeting failures Covers UI automation issues only

Recordings complement logs; they do not replace clear Log Message entries and meaningful exception messages.

Before You Enable Recording

Confirm the robot and System Activities versions support the option you want.

For queue transaction recording, check that the process sets statuses with Set Transaction Status rather than HTTP calls.

Decide who needs Execution Media View and grant it only to them.

Plan to download important videos before the retention period ends.

Privacy and Governance

Recordings may capture customer data shown on screen. Before enabling Record all jobs in production:

Check whether the screens contain personal or financial data that policies restrict.

Limit Execution Media View to the people who troubleshoot the process.

Prefer failed-only recording in production.

Remember that downloaded videos leave Orchestrator's retention control.

Scenario

A performer fails about once a week with "element not found" on a web portal, and the logs do not explain why. The developer enables Record and store failed queue transactions on the process. The next failure's video shows a cookie consent banner covering the button. The developer adds a Check App State step that dismisses the banner, and switches recording back off once the fix is verified.