“Enable Troubleshooting” no longer allows UiPath Studio access (Machine Template)

Help Orchestrator
1

Hi,

I’m running into an issue with UiPath Studio connectivity that seems to be a recent behavior change.

For a long time, my workflow was very simple: I used a Machine Template in Automation Cloud, enabled “Troubleshooting for 60 minutes” for the machine, and then opened UiPath Studio on that machine. Studio worked normally without logging in to Orchestrator, without Client ID, and without any explicit user authentication. This was very convenient for temporary access and debugging, and it worked reliably.

Now this no longer works. After enabling troubleshooting, Studio always asks to connect to Orchestrator. Logging in via Machine Key fails with an error saying that no unattended robot can be found for the user key. Logging in via Client ID also does not allow Studio to connect. It looks like enabling troubleshooting no longer grants Studio access at all.

From the behavior, it seems that Studio now strictly requires explicit user-based authentication, Studio entitlement, and folder membership, and the old troubleshooting-based access is ignored. If that’s the case, then this is a breaking change compared to how it worked before.

I’d like to understand whether this behavior was intentionally changed recently, and whether there is still any supported way to use UiPath Studio on a machine via troubleshooting / machine trust only, as was possible before, or if Client ID / user login is now mandatory in all cases.

I’ll attach a screenshot of the error for reference.

image
image703×477 50.3 KB

Thanks.

1 Like
2

Hi @Mykhailo_Nedielkov

Could you please try to login with client id by below steps go to UiPath assistant in that preferences login with client id
As per my knowledge it is failing due to no unattended robots exists for the user
As well check the machine is mapped correct folder or not.
Hope this works!

3

Hi @Mykhailo_Nedielkov

Check permissions:
For more:

Happy Automation

4

Hi @Mykhailo_Nedielkov

Troubleshooting sessions no longer grant Studio access without a licensed user/robot.

Root cause: Studio requires user-based licensing + folder access. Machine troubleshooting only enables job execution, not Studio licensing.

Fix:
Create user → Assign Studio license → Add to folder
Sign in from Studio with that user credentials
OR
Use Client ID for Robot user with Studio license + folder access

No machine-only Studio access anymore - this is intentional per current docs

5

Hi @Mykhailo_Nedielkov

This is expected behavior now. Studio no longer works based only on machine trust or troubleshooting mode. Troubleshooting still allows robot execution, but Studio always requires a real user login with Studio license and folder access. Machine Key works only for unattended robots, not Studio. So yes, this is a behavior change, and there’s currently no supported way to use Studio without user-based authentication.