Getting error in modern folder for bot allocation

Hi,
Recently I have migrated all the classic folders to modern folders in orchestrator.
I have 12 attended robot license. While creating machines in modern folder its shows as below.


How to resolve this

@rajeshigs99

Welcome to the community…

Did you happen to assign the licenses to the users after migrating?

Are machien templates created and added to the folders you need

Are the users who are given license also assigned to the folders

Cheers

While creating Machine I am getting like this. But allows to create a machine. Once after machine created I have created a new process by assigning the same machine what I have created. Then while triggering the job getting error like this

@rajeshigs99

For running in unattended while creating the robot or user you have to provide thec redentials…you did not provide i guess

and for machines as explained assign a license

First go to admin page and given licenses to tenant and then you can assign them to user and link machines and add machines and users to folders

cheers

Thats not creating a machine, thats starting a process and selecting a machine. Create a machine template and assign the licences to it, you must remove them from the classic folder first.

Make sure your robots are connecting to the orchestrator with that machine template.

As said I have created a machine with machine template. But I am unable to assign license to it (I have only attended robot license )
After this I have created a modern folder–>Process–>assigned machine to the process
But while starting the job it asking for account and machine.

You can’t run an unattended robot without assigning unattended licences to the machine template. Attended robots are for attended processes. Sounds like you were maybe breaking your licence terms and running an unattended robots via attended licences?

Okay, In modern folder can we run attended bot. If yes can you suggest me the steps for it.
Because I have only attended robot license and its working good in classic folder. But when I migrated from classic folders to modern folder I am unable to allocate the license for the machine which I have created in machine template.
Do we need unattended robot license for modern folder??

Yes, you can run attended bots. You go into the assistant and start the process.

You cannot trigger them as you were, which I believe was violating your licencing agreement and running attended bots for unattended executions. Perhaps you can explain your setup more and why you are triggering attended processes from the orchestrator?

I have 12 attended named user license (Activated the license accordingly)
image

Now I have created a machine with machine template as below

Next I have created a modern folder
image

I have assigned the above created machine to the modern folder

Then I have created a new process

Now in the respective machine I am connecting the bot from assistant. But getting license error like this

@rajeshigs99

Did you create the user? and assigned user also to folder and provided the attended lciense to the same user?

And also please click on sign in and login to orchestrator

cheers

Can you please give me the detailed steps for creating a user and assigning it to the folder and license.

@rajeshigs99

Please check these links in the document provided below

cheers

@loginerror

I think you need to report this.
Seems clear to me this user has been breaking his licence agreement for many years by using attended licences for unattended processes and has now got stuck due to Modern folders preventing that misuse.

An attended licence is only $1,200 as its supposed to have a limited scope.
An attended is $8,000.
So with 12 licences thats a difference of $81,600…
Pretty serious figure that I can see UiPath being upset with.

Hi @rajeshigs99

Without jumping to conclusion too quickly, I’d simply suggest you to contact our Cloud Support or License support via either of these forms:

The team will be able to directly help you out with your configuration.

On a quick look. If the user groups are set up correctly in your Cloud to distribute the available licenses, it looks like using the image button by the target attended user should resolve this warning:
image
I assume the goal is not to run those unattended, which won’t work here either way with just an attended license.

Hi @loginerror

I have contacted the support team, they gave clear explanation and sorted out the issue.
Now its working fine.

1 Like

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.