Queues manage workload priority and execution, with Standard queues handling routine tasks efficiently and Express queues prioritizing urgent, time-sensitive work.

Queues in Automation 360 offer a structured and scalable way to manage high volumes of work items by separating task submission from execution. This enables asynchronous processing, where bots can fetch tasks from queues based on their availability, leading to optimized workload distribution and minimal idle time. WLM supports different queue types to help organizations manage and prioritize their automation workload effectively. Two of the commonly used queue types are Standard and Express queues.

Note: In a multi-user environment, you can add a device only to one device pool.
A standard queue manages work items that do not require immediate execution and can follow regular queue rules such as First-in, First-out (FIFO) or priority levels assigned during configuration. It is ideal for routine, non-urgent processes. Some of the common examples are:
  • Weekly payroll automation
  • Routine invoice data processing
  • Back-office form validation
  • Periodic report generation
An express queue ensures that critical work items are executed as soon as possible, even if it means preempting tasks from standard queues. It is designed to meet strict deadlines and prevent SLA breaches. Some of the common examples are:
  • Fraud detection alerts
  • Real-time payment approvals
  • Urgent regulatory compliance reports
  • Time-sensitive customer service escalations
The below table describes the comparison between standard and express queues in WLM:
Feature Standard queue Express queue
Purpose General-purpose task processing Time-sensitive or high-priority task processing
Execution priority Normal Highest
Latency Moderate Very low (near real-time)
SLA support Supports SLA parameters Strong SLA enforcement with minimized wait times
Bot assignment Based on availability and queue order Immediate bot assignment to reduce processing delays
Use case examples Invoice processing, data entry Fraud detection, urgent escalations, critical transactions
Throughput optimization Suitable for batch or scheduled automations Optimized for rapid, continuous automation workflows
Resilience and retry Supports retry logic Supports retry logic
Monitoring and reporting Standard visibility Enhanced focus on SLA and response tracking
See the following table for details of the tasks you can perform as a queue owner, participant, or consumer.
Owners Participants Consumers
Can perform
  • View the queue
  • Edit the queue
  • Add other owners, participants, or consumers to the queue
  • Add work items to the queue
 Can perform
  • View the queue
  • Add work items to the queue
 Can perform
  • View the queue
  • Run bot with queue
Cannot perform: Run bot with queue Cannot perform: Run bot with queue Cannot perform: Add work items to the queue

Queue owners and participants: Note that queue owners can edit a queue (change the queue name, description, add or remove owners, participants, or consumers), but participants cannot edit the queue.