**[Assistant Connection Issue] Assistant stays orange and autogen is not created in Community Plan environment**

Help Assistant
1

Hello UiPath Community,

I’m currently using the free Community Plan to evaluate and test UiPath, but I’ve encountered a persistent issue:
When inviting a new user and having them connect UiPath Assistant, the status never turns green (Connected, Licensed), and the autogen\xxx_local user is never created in Orchestrator.

:downwards_button: Current Setup and Preconditions

  • Plan: UiPath Community Plan (free)
  • The user is invited using a Gmail account
  • On the owner (host) side, the following settings are configured in Automation Cloud:
Item Setting
Group Invited as part of “Automation Users”
Folder assignment Role: “Automation Users”
Access Rule Default: “Allow to be Automation User”
UI Profile Standard
Personal Automation Enabled (“Enable personal automation + Personal workspace”)
License type Attended User

:downwards_button: Steps performed on the user’s side

  1. Received invitation from the owner → Clicked “Accept Invitation” using their Gmail account
  2. Uninstalled Assistant and deleted %appdata%\UiPath folder
  3. Reinstalled latest Studio (Community Edition) which includes Assistant
  4. Launched Assistant and signed in with Gmail account
  5. Logged in to Automation Cloud (via browser) and confirmed the user is part of the correct host organization

:downwards_button: What is happening

  • Assistant shows as signed in, but the status is always :orange_square: orange (connected but no license)
  • No autogen\xxx_local user appears in Orchestrator under “Users”

:downwards_button: Already confirmed / tried

  • AppData reset: %appdata%\UiPath cleared
  • Assistant is the latest version
  • Confirmed that the connected organization is the correct one (host side)
  • Verified no prior Orchestrator connection remains active

:red_exclamation_mark: Current Issue

No matter what I try, Assistant never turns green (Connected, Licensed)
and autogen\xxx_local is never created in Orchestrator.

I believe that with the configuration above, Assistant should connect properly and autogen should be created automatically.
If anyone has successfully connected under similar conditions (Community Plan + Gmail user), I’d really appreciate hearing about any differences in setup or steps.

:folded_hands: What I’d like help with:

  • Successful connection examples using Community Plan + Gmail invited users
  • A reliable flow to trigger autogen creation
  • Any other potential causes why Assistant stays orange

Thanks in advance for your support!

2

Hi @aigahome,

If you go to Automation Cloud → Orchestrator → Tenant → License
What does this page show in relation to Attended User licenses?

Can you go to Automation Cloud → Admin → Licenses
How many Attended Licenses do you have allocated to any tenant vs how many total?

And the same for Automation Cloud → Admin → {Your Tenant Name} → Licenses
How many Attended Licenses are allocated to the desired tenant vs how many total?

You can also go to %localappdata%\UiPath\Logs in Windows File Explorer and open the newest 2025-XX-XX_UiPath.Studio.log and see what it say about licenses

Thanks

3

Hi @aigahome

Could you please run below command in command prompt to verify the domain/username

At the Cmd prompt, type “whoami” and press enter

It will display domain along with username. Then verify whether user is same that you are expecting?

Also, please share the screenshot from license screen.