Hi There,
Quick question on priorities at Queue level. Assuming there 10 QueueItems each in 2 seperate Queues in UiPath Orchestrator. Is there a way to prioritize QueueItems of one Queue over the other.
Regards
Hi There,
Quick question on priorities at Queue level. Assuming there 10 QueueItems each in 2 seperate Queues in UiPath Orchestrator. Is there a way to prioritize QueueItems of one Queue over the other.
Regards
Hi!
Priority of jobs are not impacted by the priority of queueitems.
You would need some way for your orchestrator to dynamically allocate robots and job priority based on volume and priorities within the queues. Either through 3rd party software like C TWO UiPath + C TWO, Simply Better Together or you could make your own tool or build a monitoring process.
You can set SLA for queueitems within queues Orchestrator - Queues SLA, but the only use for them as it stands are getting warnings if you are in risk of SLA breach.
When you configure the robots to fetch Queue Items, they will pick items based on priority first, then the oldest items. If two Queue Items have the same priority, the oldest one will be picked first.
Interesting! How you are passing two queues to the bot and why to complicate this by two queues?
I would recommend against trying to solve this with a third party solution like that, especially cause the claims made by TWO seem quite dodgey compared to the Terms and Conditions in the UiPath licence so I wouldnt trust what they offer. I think most of the problems they claim to solve can be better solved directly in UiPath with better infrastructure.
You can set job priority on a queue trigger, so if you consider one queue more important than the other you can set it up so that it creates higher priority jobs, however if a job is already running it won’t stop based on another job being pending that has a higher priority.
To do this you would need to build in a check in each process to evaluate if there is a higher priority job waiting, which is my experience can be expensive in terms of the number of API calls and not worth it.
Perhaps you can explain use case abit more and we can suggest other strategies?
Hi Sekhar,
You can pass queue name while creating process through an argument. In this case 2 process will be created for 2 different queues with same package.
It will run 2 separate jobs for both queues. While adding queue items provide priorities to items.
While creating triggers you can specify the high priority to process with specific Queue.
hope this works for you…
C TWO is the new name for a product called RPA Supervisor which is a legitimate tool.
RPA Supervisor - RPA Component | UiPath Marketplace | Overview
(It was/is basically required if you’re running a large scale Blue Prism deployment)
I agree with what you’re saying though, it’s more effective to ensure a strong infrastructure within the UiPath environment itself.
Hi Sekhar,
You can set priority for QueueItems. Each QueueItem in UiPath can be assigned a priority between normal, low and high. You can prioritize the QueueItems in one queue over another by setting their priority values accordingly.
What Happens Behind the Scenes:
Low: This will typically assign a priority value of 100 (the lowest priority).
Normal: This usually corresponds to a value between 50 and 60.
High: This assigns a value between 1 and 10, making it a higher priority.
I’m fully aware of the product, and I have discussed some stuff with them and UiPath, it does not seem compliant and I do not trust them.
I see, and I trust your assesment. I’ve sent you a DM
can you tell the use case for this …may be we can try helping with a better approach based on it
cheers
@Anil_G , Its a simple use case. I have two seperate queues, two seperate automations in two seperate folders. One process has imprtance over the other. While jobs of a low-prio process are running all machines parallelly, if queueitems land in the queue of a high-prio process, i want these to take precedence …
Hi @Sekhar
To manage two separate queues with different priorities , you can implement a priority queue system. While jobs from the low-priority process are running, monitor the high-priority queue. If new items land in the high-priority queue, pause the low-priority jobs and execute the high-priority jobs first. This ensures that high-priority tasks take precedence over low-priority ones, maintaining efficient workflow management.
Happy Automation
Monitoring them and stopping the process is the way ..get queue items and then check new filter
cheers