11.2 Queue Items SLA, Postpone, Deadlines & Priority Scheduling

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:

1. Eligibility filter. Only New items whose Postpone date is empty or already passed are considered.
2. 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.
3. 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:

Evaluation at 10:00 AM:

1. Eligibility. Item_5 is postponed until 10:30 AM, so it is skipped for now.
2. 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.
3. Items without a deadline: Item_3 (High). It comes only after every eligible item that has a deadline.
4. 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:

1. 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.
2. 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: