Refer to this FAQ for general queries about the features and functionality of the parallel queue processing in Workload Management (WLM). This is designed to provide answers to generic questions that you might encounter while using the parallel queue processing feature.

What is parallel queue processing?
Parallel queue processing is a method that allows multiple queues to be processed simultaneously on devices.
What problem does it solve?
WLM has a limitation when handling multiple queues within a device pool. If two or more queues are present, only one queue can be active and processed at any given time. However, using parallel queue processing allows multiple queues to be processed concurrently on devices.
What are the key benefits of parallel queue processing?
There are multiple benefits of parallel queue processing, such as faster SLAs, improved resource utilization, and so on. For more details, see Parallel queue processing - key features.
What version of Automation 360 introduces parallel queue processing?
Automation 360 version 37 introduces the capability for parallel queue processing, allowing for more efficient task management.
Is the parallel queue included in the base license?
Yes, the base license includes access to the parallel queue feature.
Is the parallel queue available for On-Premises and Cloud?
Yes, the parallel queue feature is available for Automation 360 On-Premises and Cloud deployments.
Does it work for device pool and terminal server?
The parallel queue automatically operates on default devices, eliminating the need to select a device pool. To deploy work items effectively, follow these steps:
  1. Select a WLM bot.
  2. Choose a queue.
  3. Assign run-as users with default devices.
Will the parallel queue automation be available on the device pool details page?
No, parallel queues do not use the device pools. Therefore, you will not find information about parallel queues on the device pool details page.
Does parallel queue work in round-robin or priority mode?
No. Parallel queues operate independently of device pools. As a result, round-robin and priority modes do not apply to parallel queues.
What happens if devices are processing in a parallel queue and if a high-priority WLM automation is deployed?
In this scenario, the parallel queue will keep running, which means that high-priority WLM automation must wait until the parallel queue processing is finished. For further information, refer to the Scenario deployment use cases.
Can I use the same resources (run-as users and devices) for parallel queue and device pool (round-robin, priority) mode?
No, we recommend using separate resources for parallel queue and device pool modes. Do not mix these resources.