Orchestrator Skip queue item, Cancel in-progress, Password assets


I have a few questions about orchestrator.

  1. Is there a way to continue transaction items in the orchestrator queue after a failed business or system error? For example: I have 5000 orchestrator queues lining up and a item fails at item 1123. I want it to continue for another 10 transaction items and if they all fail as well the whole process should be stopped. Else, just continue with the rest of the items.

  2. is there a way to force stop in progress orchestrator queues. Like force killing the item without needing to re-enter the queue item.

  3. Credentials stored in orchestrator seem “safe”. But once you know the orchestrator asset for the credentials you can (if you have access to those assets) enter them into any other “secure” input field and read them out. How to securely secure credential assets within orchestrator without other people being able to access it?

Thanks in advance :slight_smile:


Ps: Uipath forum admins, add the word “Uipath, orchestrator” to your dictionary (if this isn’t managed locally) :slight_smile:

Since I didn’t get an answer yet, i’ve made a workaround.
I think i was focusing to much on Orchestrator, instead I can handle point 1 within the workflow of a robot.
After correct handling of the try-Catch and error handling i got point 1 sorted out i think. Would still be nice to have it as an option within Orchestrator next to the Retry option. Something like “Skip x-times failed items until process failure”.

Point 2 and 3 im still trying to figure out so feel free to brainstorm :slight_smile: .


Point 2: There are two options available in orchestrator to stop the job, Stopping a Job and Killing a Job. Killing a job is the answer to your question. For detailed explanation, please go through below link:

Point 3: Multi-tenancy enables you to isolate data,for different tenants within in single instance of Orchestrator. Two different tenants won’t be able to see internal data of each other. Please have a look on this concept in below link:

Roles concept will help you out in securing credentials. You can define roles to each user and give them permissions to view or update the assets and credentials. Ideally, Only Administrator role should have right to update the credentials.

I hope this helps you in resolving your queries. Let me know incase of any query.

Hi @singhonkar
Thanks for your reply. Some questions remain tho.

Point 2: Killing a job or terminating it kills the job process. But sometimes in happens that a Queue item in the queue stays on “in progress” (due to failure etc). This queue item will get to status failed in 24 hours after no result. Killing a job or terminating it does nothing to the queue item that has status “in progress”. Still the retry option remains unavailable until the queue item is failed or you have to re upload it. I’m still looking for a way to kill the “in progress” status for a queue item.

3: Its good that the role permission can block people from updating the credentials. But the fact still remains that once you have access to a credential asset (from developers perspective) you can still abuse that information in a way to ready the secure data. For example: A developer that needs access to the credentials to log in to a system, but hasn’t got rights to modify the credentials can still make a workflow pointing the input to a “secure” input field and read or show the password information.

Point 3 might just be an impossible issue to solve, since giving access to credentials also grands abuse to the user, but was just wondering. Maybe it could be solved by having the credentials stored with a target location or something, so that it can ONLY be used on a certain field withing a certain environment and got user input blocked by default.

I hope i got my issue across properly, and maybe you have some thoughts about it :slight_smile:

Thanks in advance!

1 Like