TryCatch for duplicate items in Orchestrator queues


#1

I have a queue that works the transaction items then adds them to another queue. In one instance I may need to postpone the TI in the first queue a week but still need to add it to the second queue for notation processing. My issue is when I rerun the first transaction it will want to add the same reference number to the second queue which will throw an error. If I use a TryCatch will catching System.Transaction.TransactionException be too large of a net? There doesn’t seem to be a catch for Duplicate Reference Error Code: 1300.


#2

This exception is thrown because your queue enforces unique reference.
see https://orchestrator.uipath.com/docs/managing-queues-in-orchestrator

This option is available when you create the queue.

Is this set on purpose?

Cheers