After Upgrading Studio and when Running a Process Getting an Error Message that 'Automation Cloud Cannot Be Accessed. This May Be due to Network Fluctuations on the Machine Running the Robot'

News Knowledge Base
1

Why am I getting 'Automation Cloud cannot be accessed. This may be due to network fluctuations on the machine running the Robot' error?

Issue Description

In UiPath studio 2025.0.166, an error can occur when a process tries to use an Automation Cloud service (such as sending email via UiPath’s integrated email service).

The execution fails with an error:

Send Email: Automation Cloud cannot be accessed. This may be due to network fluctuations on the machine running the Robot.

Root Cause

Even though the robot appears connected, the update to Studio version introduced an authentication mismatch. When using cloud services or Orchestrator with SSO, the existing connection token may no longer be valid after the update.

In essence, the robot could not actually reach Automation Cloud resources despite the UI showing it as connected. The underlying cause is similar to the robot’s authentication method (machine key/SSO token) that is no longer accepted, requiring a re-authentication with the cloud.

Resolution

The solution is to re-establish the robot’s connection to Automation Cloud using updated credentials. This involves recreating the machine entry in Orchestrator and updating the robot configuration, as described below:

  1. Disconnect the Unattended Robot from Orchestrator.
  2. In Orchestrator, delete the machine/machine template that the Unattended Robot is using.
  3. Re-add the machine (or create a new Machine entity). Copy the new Machine Client ID and Client Secret that are generated for it (as described here).
  4. On the Robot machine, open UiPath Assistant. Go to Orchestrator settings, sign out if already signed in. Choose 'Connect using Machine Credentials' and input the new Machine Client ID and Secret (as explained here).
  5. Once reconnected, verify the UiPath Assistant shows the robot as connected and licensed.

After following the above-mentioned steps, re-run the email sending process. The “Automation Cloud cannot be accessed” error should be resolved, as the robot now has a valid authentication to connect to Automation Cloud services.

Note 1: In summary, for any cloud connectivity errors right after an update, re-registering the robot with Orchestrator (using the modern authentication method) is a reliable fix. This forces a refresh of the connection tokens and resolves issues caused by outdated credentials.

Note 2: If using Google SSO for user authentication, an extra step is necessary. In Orchestrator’s Machine details, generate a robot key (Secret) for the Unattended Robot user. Use this secret when reconnecting the robot so that it can authenticate via SSO.