I possess these robots within the folder “Estudio Clemente”. It is imperative that they do NOT execute unattended on Machine A (my development machine), yet they should operate on Machine B (my production machine, Windows Server).
However, upon execution, an error occurs, indicating that there are no licenses available for unattended robots.
2026-01-05 17:57:36.000 GMT−3: Error: Incident at element task_atp: Failure to initiate the Orchestrator RPA job.
Failure to initiate the Orchestrator RPA job - (170007). No user with permissions for the unattended robot could be found in the current folder.
It’s necessary to assign user or robot account to the folder.
Which account do you assign?
If it’s the above AutomationUser role user, can you add UR settings (windows credential etc) at Tenant -Manage Access - choose the user and Edit, as the following?
Well, I have added a Robot Account. This account was created so long ago that I can’t even remember how I did it, so it might have some configurations that are not quite appropriate. We’ll see.
Do you already have machine template?
We can connect UR with Orchestrator using ClientID and secret from MachineTemplate page. In assistant Connection Type: ClientID can be used.
I once had a robot that was neglected, so I deleted it to recreate it properly, but now I am unable to create it again.
Have the community license changed? Is it possible that I can no longer create unattended robots, not even one as I used to?
Can you elaborate your problem? Community plan still has Unattended Robot license and we can use it. However, community installer may not support service mode installation.
[/quote], I previously had an account named RobotX, which was of the Unattended type. Since I had created it a long time ago and could not recall how I had done so, I decided to delete it by following these steps: I navigated to Tenant > Manage Access > Robots, clicked on the three dots, and selected ‘Unassign.’ As you can see, RobotX is no longer present.
Afterward, I clicked on ‘Assign Robot Account’ and followed the procedure to create an Unattended-type robot. However, when I attempted to finalize the process, it informed me that I had reached the maximum quota.
[/quote], I previously had an account named RobotX, which was of the Unattended type. Since I had created it a long time ago and could not recall how I had done so, I decided to delete it by following these steps: I navigated to Tenant > Manage Access > Robots, clicked on the three dots, and selected ‘Unassign.’ As you can see, RobotX is no longer present.
Afterward, I clicked on ‘Assign Robot Account’ and followed the procedure to create an Unattended-type robot. However, when I attempted to finalize the process, it informed me that I had reached the maximum quota.
Well yes those are enforcements even if you delete the old robots…upgrade the plan or if you want community and if its ok to recreate…delete the org and recreate so that you get a fresh quota
If you get a new org you can do all..with the current one there would be limitation to create more users as users quota limit is reached
You can still go and create maestro processes even now and debug them as well
Hello, I have successfully created the machine, obtained the secret and the machine key, but when I attempt to join, I encounter the following exception: System.Exception: “https://cloud.uipath”.com/rpasisve/rpasisve/odata/Settings, status NotFound, reason Service Not Found"
The URL of my orchestrator is “UiPath” but ChatGPT suggested trying to add “rpasisve” again. However, it still does not work.
Perhaps it is because I have the Community version and did not change the name of the DefaultTenant? Should I access “UiPath Orchestrator”? Is my assumption correct?
