Good Practices into Orchestrator Queues

Hello guys.

Please, help me find out the good practices about design the solutions when queueing workitems using Orchestrator…

  • How do I assure that a workitem wont be duplicated into Orchestrator queue?
  • If I get an error into a WorkItem, how can I re-execute this workitem if I am handling to not duplicate items into Orchestrator?


Hi @Mateus_Oliveira
For your first question

  1. To avoid duplication issues you should set a unique reference no for each queue item when it is added using add queue item
    It is unique for every queue item so the duplicates data will not be entered

  2. I think what i understands about second query is regarding the retry mechanism of queue item
    First to make queue item retry , we should set autoretry as Yes with retry number value >0
    Like whnever when some application or system exception occurs in workflow while executing the process we should update queue status as Failed along with reasons like Business Exception or Application Exception using set transactional status activity in UiPath. In case of Business Exception bot will not retry that queue item as there is no mean of retrying it again (because that error occured some error in data which cannot be rectified via retrying again and again). So when system exception occurs the queue status will updated as Retry due to Application exception and add a queue item of same type again and process it (it will retry upto max retry no for queue which user / developer has defined)

Hope it helps


Nived N
Happy Automation

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.