Study guide

13.1 Unattended Job Execution: Folders, Priorities, Background vs. Foreground & Runtimes

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

13.1 Unattended Job Execution: Folders, Priorities, Background vs. Foreground & Runtimes

Key Takeaways Explain This Topic AI

Unattended jobs start from the Jobs or Processes page or from time, queue, event, and API triggers, and run in a folder with a process, an account, and a machine template.

There are ten job priorities; a free robot receives the highest-priority pending job, oldest first on ties, and triggers and manual jobs default to the Inherited process priority.

The API maps priorities to values 1 to 100 through SpecificPriorityValue, for example Critical is 91 to 100.

Background processes can run concurrently, but one account runs only one foreground process at a time on a machine.

Runtimes on a machine template set how many unattended jobs each connected host can run at once; without free runtimes, jobs stay Pending.

Last updated: September 2026

13.1 Unattended Job Execution: Folders, Priorities, Background vs. Foreground & Runtimes

Core Concept: The exam description lists "Unattended automations features: Folders, job priorities, background vs foreground processes, license per machine". This section explains how Orchestrator decides which job runs next , on which account and machine , and how many jobs a machine can run at once .

What a Job Is

A job is one execution of a process on a robot. Unattended jobs are launched from Orchestrator, either directly from the Jobs or Processes page or through triggers (time, queue, event, or API). Attended robots cannot run jobs started from Orchestrator, except for debugging and development.

Job States

  • Group States Meaning
  • Initial Pending Waiting for a robot or for a connection to it

Active Running , Stopping , Terminating Stopping follows Stop (a graceful end the workflow can honor with the Should Stop activity); Terminating follows Kill

Intermediate Suspended , Resumed Long-running workflows waiting for a task, job, or queue item

Completion Successful , Faulted , Stopped Faulted jobs failed to start or threw an unhandled error; they must be restarted manually

A job ended with Stop finishes as Successful , while a job ended with Kill finishes as Stopped .

Folders and the Execution Target

A process, its jobs, and its triggers live in a folder . For a job to run, the folder needs:

The process (a package version deployed to the folder).

An account (user or robot account) assigned to the folder with unattended settings.

A machine template assigned to the folder, with runtimes, and a host machine connected with that template.

When starting a job you choose the execution target :

Option Behavior

Allocate dynamically Orchestrator picks any account and machine that becomes available. A process can be run up to 10,000 times in one job request this way.

Account Runs under the chosen account; the machine is picked dynamically.

Machine Runs on a host of the chosen machine template (optionally a specific Hostname ); the account is picked dynamically.

Account-machine mappings Runs on specific account-machine pairs, one pending job per pair (requires the tenant setting that enables account-machine mapping).

For foreground jobs, each account must also exist as a Windows user on the host machines connected through the template.

Job Priorities

A job can have one of ten priorities. From lowest to highest: Lowest, Very low, Low, Medium-low, Medium, Medium-high, High, Very high, Highest, Critical .

How Orchestrator allocates pending jobs

A robot becomes available.

Orchestrator identifies that robot's machine template and every folder the template is assigned to.

It evaluates the pending jobs from those folders.

It gives the robot the job with the highest priority . Jobs with the same priority go out oldest first .

Where the priority comes from

The process has a priority.

Jobs started manually and triggers default to Inherited , meaning they use the process priority.

A trigger with its own priority passes that priority to the jobs it launches.

The API view: 100 levels

The ten UI levels map to 100 API values through the SpecificPriorityValue parameter (for example on StartJobs and ProcessSchedules ):

  • Priority API range Default
  • Lowest 1–10 5
  • Low 21–30 25
  • Medium 41–50 45
  • High 61–70 65
  • Critical 91–100 95

Two jobs with values 92 and 94 are both Critical, but the job with 94 runs first .

Background Versus Foreground Processes

Background process Foreground process

User interface Needs no UI interaction (APIs, files, data) Needs UI interaction ( User interaction: Required on the Jobs page)

Concurrency on one machine Several can run at the same time, even under the same account, as long as runtimes are available One account can run only one foreground process at a time on a machine

  • Session Runs in the robot service's context Needs an interactive Windows session for the account
  • Typical use Dispatchers, API integrations, data processing Desktop and web UI automation

On a machine template you can also restrict the process type the machine accepts: foreground only, background only, or all.

License per Machine: Runtimes

Unattended capacity is expressed as runtimes allocated to a machine template . Each runtime allows one concurrent unattended job on each host machine connected with that template. For example, a template with 2 unattended runtimes lets every connected host run up to two jobs at once, which on a Windows Server host with several accounts means two sessions in parallel. Without free runtimes, new jobs stay Pending .

Keeping Jobs Healthy

Schedule ending of job execution: stop or kill a job that stays Pending or Running too long.

Keep account-machine allocation on job resumption: by default a resumed long-running job can continue on any available robot; this option keeps the original pair.

Robot reconnects: if a machine goes down or the robot service crashes during execution, the robot restarts its running jobs after reconnecting.