Quota reached - cannot add new Robot accounts

Help Orchestrator
, , , ,
1

Hi,

I am experiencing an issue with creating new Robot accounts in admin and/or Orchestrator. I am using Community Edition, so using cloud.uipath.com for access.

Earlier today I was experimenting with creating a new robot account, which worked. Settings were not OK, so I deleted it. When trying to create a new robot account, I get the error “Quota reached”.

I searched in the documentation:

“When the limit for a particular resource is reached, the system throws the following error: “Quota reached, cannot create more objects”. To add new objects, you can upgrade your licensing plan.” which has to do with the Resource quota enforcement

So I tried deleting all other robot accounts: I now have 0 robot accounts.
This is visible in (Admin) > Accounts & Local groups > Robot accounts and at Tenant > Manage Access > Access Rules > Robot Accounts

Issue still persists.

What I already have tried:

  1. Tried creating Robot accounts through (Admin) > Accounts & Local groups > Robot accounts (https://cloud.uipath.com/{userid}/portal_/admin/identities/robots)
  2. Tried creating Robot accounts through (Orchestrator >) Tenant > Machines > Unattended setup > Create robot account
  3. Tried removing Unattended and Test license from the Tenant and adding back to it

I have searched the forum, users that also experience the same issue:

What I suspect the issue is, is that for Community Edition the max local users/accounts is set to 10. I think these are ‘soft deleted’; meaning not visible for me anymore, but that they still exists in the backend and count towards the total count of 10. Through the many years and my latest activity of adding one, I might have hit this 10? Or some caching issue?

What was also surprising is that I get different errors depending on the process:

  1. “Error adding new production (unattended) robot.” at step #1 of above list
  2. “Quota reached, cannot create more objects” with a session ID (it displayed this error in stead of #1 one time)
  3. a Japanese (?) error on step #2 of above list - it translates to Quota reached

Suggestion to delete my entire account would be a shame: I would loose all my configuration, settings, history etc. (I’ve been using this since 2017 or so

errorQuotaReached_Admin_SessionID
errorQuotaReached_Admin_SessionID2036×894 68.6 KB

errorQuotaReached_OrchLicenseOverview
errorQuotaReached_OrchLicenseOverview1842×704 59.9 KB

errorQuotaReached_Japanese
errorQuotaReached_Japanese1202×1019 79.6 KB

A software interface displays an error message on the right side while attempting to add a new robot account, with no data currently visible in the account list. (Captioned by AI)
A software interface displays an error message on the right side while attempting to add a new robot account, with no data currently visible in the account list. (Captioned by AI)2035×964 38.1 KB

…)

3

@Bolletje

so basically there has been a change in license as well which is named user license…so once it is tagged to a robot or user then the quota limit wouls still come even if you delete as it is tagged

the way you can get the quota is to delete the organization from admin page and then recreate a new org again in community version(not tenant but org)

cheers

4

@Anil_G hey Anil, thank you for your reply.

Do you have more information about? Where did you get the tagging information?

It is not very clear from the documentation and other posts that this is the case. One would expect that if limit is reached (e.g. 10), that it will show how this is achieved. (like is the case with licenses). In my case, I have 0 robot accounts, and unable to add new ones. So that would mean the entire setup is broken for unattended setup. Looks like an issue then.

I get your idea of deleting Organisation and creating a new one. I will wait a bit longer before I do such rigorous action.

5

@Bolletje

one way it might help try checking is via your audit logs on how many users are created

I agree the documentation was little confusing

This was an issue recently that many have reported after the change of quota limit introduction itself..but the limit is not shown as you mentioned

The image is a text excerpt explaining that when a resource limit is reached in UiPath, an error is thrown, prompting users to upgrade their licensing plan or contact UiPath Support for assistance and provides details about resource quotas. (Captioned by AI)
The image is a text excerpt explaining that when a resource limit is reached in UiPath, an error is thrown, prompting users to upgrade their licensing plan or contact UiPath Support for assistance and provides details about resource quotas. (Captioned by AI)947×205 23.6 KB

as mentioned here once quota reaches you need to upgrade but in case you are not willing to buy you can create…if you want to buy a plan or upgrade to enterprise trail can try that too..but again after the trail period it returns to free

or other way is contact support team where you might need to give a license code which in the case of community would not be available..

cheers