Serverless robot cannot be used

Agentic Automation Associate Training

  • Building your first agent in UiPath Studio Web
  • Creating a self-sufficient agent from scratch (Reservation Management Agent)

I am currently studying this.

I successfully published it, completed the setup, and tried to run it, but I encountered an error.

Serverless.Api.PersonalAutomationCreditsExceeded - Automation cannot be started. Your user’s monthly Personal Automation quota has been exceeded.

It appeared, but since this was my first run and I haven’t used it at all. I’m on the Community Edition.

I specified the tenant when publishing the agent according to the materials, but was it supposed to be a personal workspace?

Hello

First, I think it would be a good idea to check the current license consumption status in AutomationCloud under Management - License consumption type.

Thank you very much!
I see. This means there are still some issues, right?
Is it because user management is not enabled yet…? I will test it later.

Hello

It seems like there is a robot unit available.

The causal relationship with this issue is unclear, but it might become problematic if it remains disabled, so I think it would be better to enable it.

I published again following the steps.


The verification says it’s OK, but

It results in an error during activation.


I’m having to reattach the link every time.


When I run it, it produces the same error.

Serverless.Api.CreditsExceeded - Not enough Robot Units to run the automation. Please contact your administrator.

The robots are not being consumed.

There were no instructions regarding folder permissions or role assignments in the materials.

The workflow debug execution was successful before publishing.

Hello

It might be a good idea to troubleshoot the issue.

Here is a solution created in my Community plan environment, which uses RPA tools to return the length of a string entered by the Agent. Can you execute it successfully? (Debug run, Publish → Run)

Solution.uis (12.5 KB)

I apologize for the late response.
It started working.
The cause seems to have been that I had created an unattended user myself, and after deleting that, it started working.