Hi @roger1
Welcome to our UiPath Forum
I will make this post public because it could be information that will prove useful to other users as well.
-
I was able to easily reproduce this error on my end and I reported it to our team.
-
First, I am happy that our first run Studio experience went flawlessly for you. Main thing that makes it possible is the default simplified setup that you get out-of-the-box.
Mainly, by signing up to Orchestrator from your Studio for the first time, you get automatically connected to your Personal Workspace:
It’s purpose is to be a simplified folder that will get you going, but that will not allow you to run unattended processes. To make that happen, you will need to configure a few more things in Orchestrator.
These are these things:
Making sure your process is in the right place:
- First, make sure you publish your processes to the Orchestrator Tenant Processes Feed
(otherwise it will be set as Orchestrator Personal Workspace Feed, which we don’t want) - Create your process in the Shared folder:
Making sure your folder settings are correct:
- Assign unattended runtime to your machine under Tenant → Machines
- Enable unattended robot for your user under Tenant → Users
2a. Fill in the correct domain\username for your machine (this is important, otherwise your processes will be stuck with Pending status when you run them with the auto-generated value). You can grab your domain by runningwhoami
command in your Windowscmd
console:
- Add your user to the correct folder under Tenant → Folders → Shared → Users
- Add your machine template to your folder under Tenant → Folders → Shared → Machines
You should now be able to run a job on your machine:
I hope it’s helpful