Study guide
11.2 Queue Items SLA, Postpone, Deadlines & Priority Scheduling
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
11.2 Queue Items SLA, Postpone, Deadlines & Priority Scheduling
Key Takeaways Explain This Topic AI
Queue items have Low, Normal, or High priority, an optional Postpone date that hides them until that time, and an optional Deadline.
Get Transaction Item returns items that have a Deadline first (ordered by priority, then deadline), then items without a Deadline (ordered by priority, then first in, first out).
A Normal item with a deadline is fetched before a High item without one.
A queue SLA assigns a deadline of creation time plus the SLA to items added without one; Risk SLA and SLA predictions flag items at risk on the Queues SLA monitoring page.
Retry copies keep the item's data, reference, and priority and are New immediately; queues have no retry delay setting.
Last updated: September 2026
11.2 Queue Items SLA, Postpone, Deadlines & Priority Scheduling
Core Concept: In enterprise robotic workflows, queue processing is rarely a simple First-In-First-Out (FIFO) queue. Business operations require differentiated urgency: an expedited high-value wire transfer must supersede a routine balance inquiry, items dependent on external nightly batch jobs must remain deferred until a specific hour, and transactions bound by strict regulatory Service Level Agreements (SLAs) must be consumed before their deadlines elapse. UiPath Orchestrator achieves this through a deterministic priority and deadline scheduling engine.
When a Performer robot invokes Get Transaction Item , Orchestrator does not simply select the oldest item in the database. Instead, it executes a multi-dimensional evaluation query that weighs item Priority , Postpone timestamps, Deadline timestamps, and initial Creation Time . Understanding this deterministic evaluation logic is critical for passing the UiPath Automation Developer Professional exam and designing multi-robot transactional ecosystems that prevent SLA breaches.
1. Core Scheduling Parameters: Priority, Postpone, and Deadline
When creating a queue item—either via Studio activities ( Add Queue Item , Bulk Add Queue Items ) or through the Orchestrator REST API—developers can specify three critical scheduling properties: +-------------------------------------------------------------------------+
- | QUEUE ITEM SCHEDULING PARAMETERS |
- | |
- | +-------------------------------------------------------------------+ |
- | | Priority: High | Normal (Default) | Low | |
- | | - Orders items within the deadline and no-deadline groups | |
- | +-------------------------------------------------------------------+ |
- | | Postpone (DeferDate): Nullable<DateTime> | |
- | | - Blocks item consumption until DateTime.Now >= PostponeDate | |
- | +-------------------------------------------------------------------+ |
- | | Deadline (DueDate): Nullable<DateTime> | |
- | | - Items with a deadline are fetched before items without one | |
- | +-------------------------------------------------------------------+ |
- +-------------------------------------------------------------------------+
- 1. Item Priority
UiPath supports three distinct priority tiers:
High : Top-tier processing urgency.
Normal (Default): Standard processing urgency.
Low : Deferred or background maintenance processing urgency.
Architectural Impact: Priority decides the order within each of the two groups described below: items that have a deadline and items that do not. It does not override the deadline grouping.
2. Postpone Date ( DeferDate )
The Postpone date (represented in the API as DeferDate ) delays item consumption until a designated future timestamp.
Eligibility Gate: If an item has Postpone = 2026-10-15 14:00:00 and the current system time is 2026-10-15 11:30:00 , the item is completely ineligible for retrieval. Orchestrator treats it as temporarily dormant.
Enterprise Use Cases:
Downstream System Windows: Ingesting transactions during the business day but deferring execution until an external mainframe or SAP batch window opens at 22:00.
Rate Limiting & Throttling: Staggering API transaction payloads to avoid exceeding third-party SaaS rate limits (e.g., adding 500 items with postpone timestamps incremented by 30 seconds).
Time-Locked Workflows: Ensuring a follow-up billing transaction does not execute until exactly 48 hours after customer onboarding.
3. Deadline Date ( DueDate )
The Deadline date (represented in the API as DueDate ) defines the latest permissible completion timestamp to satisfy a business Service Level Agreement (SLA).
Operational Sorting Impact: Items that have a deadline are processed before items that have none, as the next part explains.
SLA Monitoring: When a queue has SLA predictions enabled, Orchestrator notifies users when items are at risk of missing their deadline.
2. Deterministic Item Consumption Algorithm: Get Transaction Item
When a Performer robot invokes Get Transaction Item , Orchestrator applies a rigorous, multi-tiered filtering and sorting algorithm. Understanding the exact sequence of this evaluation is essential for predicting production behavior. Get Transaction Item: order of eligible items
- 1. Filter: status New, and Postpone empty or already passed
- 2. Items WITH a Deadline: Priority (High > Normal > Low), then earliest Deadline
- 3. Items WITHOUT a Deadline: Priority (High > Normal > Low), then oldest first (FIFO)
- 4. Every eligible item in step 2 comes before any item in step 3
- The Evaluation Order Rules
Orchestrator's queue documentation describes this order:
Eligibility filter. Only New items whose Postpone date is empty or already passed are considered.
Items that have a Deadline come first. Among them, order is by Priority , and items with the same priority are ordered by Deadline , earliest first.
Items with no Deadline come next. Among them, order is by Priority , and items with the same priority follow First In, First Out .
So a Normal item that has a deadline is fetched before a High item that has none. UiPath also notes that Deadline is for ordering items of similar priority, while Postpone keeps an item from starting too early, and that the two parameters are not designed to be used together.
Concrete Scenario Walkthrough
Consider a queue at 10:00 AM with five New items:
- Item ID Priority Postpone Deadline Created
- Item_1 High None 12:00 PM 09:30 AM
- Item_2 High None 11:00 AM 09:45 AM
- Item_3 High None None 08:00 AM
- Item_4 Normal None 10:30 AM 07:00 AM
- Item_5 High 10:30 AM None 09:00 AM
Evaluation at 10:00 AM:
Eligibility. Item_5 is postponed until 10:30 AM, so it is skipped for now.
Items with a deadline: Item_1 (High), Item_2 (High), and Item_4 (Normal). Priority orders them: the High items first, by earliest deadline, so Item_2 , then Item_1 , then Item_4 .
Items without a deadline: Item_3 (High). It comes only after every eligible item that has a deadline.
Result: the fetch order is Item_2, Item_1, Item_4, Item_3 . Item_4 is Normal priority, but its deadline puts it ahead of the High-priority Item_3. Item_5 joins the no-deadline group once 10:30 AM passes.
3. SLA Tracking, Predictions & Risk in Orchestrator
In mission-critical enterprise processes (such as fraud detection, trade execution, or urgent medical authorizations), meeting business deadlines is a contractual necessity. UiPath Orchestrator provides built-in SLA Management features directly within Queue configuration. +--------------------------------------------------------------------------+
- | ORCHESTRATOR SLA TRACKING METRICS |
- | |
- | Queue Item Creation Deadline (DueDate)|
- | | | |
- | v v |
- | +---------------------------------------+-------------+-----------+ |
- | | Predicted Processing | Risk Buffer | Breached | |
- | | | | SLA | |
- | +---------------------------------------+-------------+-----------+ |
- | ^ ^ |
- | Risk SLA Trigger | |
- | | |
- | SLA Deadline Target |
- +--------------------------------------------------------------------------+
- SLA Configuration Properties
When configuring SLA tracking on an Orchestrator Queue, administrators define two core time thresholds:
SLA (Target Duration): The maximum time from item creation to processing (up to 90 days). Items added without a deadline get one automatically: creation time plus the SLA. Items that already have a deadline are not affected. Enabling SLA predictions also requires choosing the process that handles the queue, and it must be the same process as the queue trigger's.
Risk SLA (Warning Threshold): A shorter period that works as a buffer zone before the SLA. It is also measured from the moment the item was added : with a Risk SLA of 2 hours, an item added at 4:30 PM has a risk deadline of 6:30 PM. If the item is still unprocessed after that, it is at risk and users are notified.
SLA Predictions
With SLA predictions enabled, Orchestrator estimates whether the queue's items can be processed in time with the robots available to the chosen process, and it flags items as at risk when their estimated completion passes the Risk SLA point. The Queues SLA page under Monitoring shows the prediction and the items at risk.
SLA Status Classifications
In SLA: The estimated completion time is well ahead of the Risk SLA threshold. Operations are healthy.
At risk: The item's Risk SLA time has passed and it is still not processed. Orchestrator notifies users so they can add robots or change priorities.
Breached SLA: The transaction item was not completed before its Deadline timestamp expired. Recorded as an SLA violation for regulatory compliance audits.
4. What a Retry Copy Keeps
When Auto Retry creates a new copy after an application exception, the copy carries the original item's data:
- Property On the retry copy
- SpecificContent The same input data
- Reference The same reference, which keeps the retry chain traceable
- Priority The same priority
- RetryNo One higher than the item it replaces
Key and ancestry fields Link the copy to the original item of the retry chain (for example, AncestorId and Key in the API)
Note
Orchestrator queues have no "retry delay" setting. A retry copy is New immediately and is fetched according to the normal order above. If you need a pause before retrying, build it into the workflow, or add a new item with a Postpone date instead of relying on Auto Retry.