I have one packages that uploaded to the ochestrator and it is unable to click on the unattended robot as no robot is showed there.
And while using start process, it can choose the unattended robot.
Although the process faulted because there is an issue with the dependency and caused it unable to install the packages.
And wanted to ask whether the “unable to install package” is the causes that make it unable to choose the unattended robot in the trigger function there?
Or it is my workflow problems??
ps: the robot is connected to the machine as others process does not have this issue.
I tested on my personal uipath cloud. I uploaded it and add at the processes there. The column “execution type” shows Unattended.
In the environment this process ia uploaded there are no unattended bots available. Please allocate a license to make it visible here. In robots you can change the licenses
But I did have the license as when I run through the orchestrator ( without login to the server) the process is able to be run, and I also able to select the unattended robot.
It just that at the trigger there, the unattended robot didn’t shows up.
And is it because the packages is not yet install in the machine that it works?
No that might not be the issue… the process you created might be in a environment where no attended bot is assign… please see the environment of the process and cross verify if you have a unattended bot there
And that’s why I suspect that maybe it’s because the package is missing in nuget folder, and causes the unattended robot not showing up at the trigger function there.