Orchestrator user guide

DELIVERY:

Last updated Jul 1, 2025

General troubleshooting

The remote certificate is invalid because of errors in the certificate chain: UntrustedRoot

The net::ERR_CERT_AUTHORITY_INVALID error occurs when your certificate expires or is involved in a certificate rotation process, indicating that it is now invalid.

It is most likely that the error occurs for the following reasons:

You cannot access UiPath standalone product installations.
Your robot is disconnected.

To fix this error, take the steps, described in the following example:

Select the Not secure warning prompt. Then select Certificate is not valid from the dropdown menu.
In the Certificate Viewer, select the Details tab. Then select Export and save the certificate.
On your local machine, open certlm.msc and right-select the Personal folder, then select All Tasks, then select Import. Select the previously generated certificate and import it.
In the same certlm.msc window from the previous step, select the Trusted Root Certification Authorities folder, then select All tasks, then select Import. Select the previously generated certificate and import it again.
Connect the robot again to check that the error is fixed.
Select the View site information icon. Select Connection is secure from the dropdown menu.

Browser group policies

Signing in to your Orchestrator service from the Assistant redirects you to the SSO page. In some browsers, you may be prompted to open UiPath Assistant. This happens due to the Assistant's protocol handler not being added to the browser's group policies.

To prevent this behavior, make sure to follow the next steps, depending on the browser (Chrome/Microsoft Edge):

Open Registry Editor.
Navigate to Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome/ or Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Edge, depending on the browser you use.
Add a new key and name it AutoLaunchProtocolsFromOrigins.
Select (Default) to edit the key.
In the Edit String dialog, in the Value data field, add [{"allowed_origins": ["<https://myOrchestrator.uipath.com/"],"protocol":> "com.uipath.robot.oidc"}] and select OK.

Important: The AutoLaunchProtocolsFromOrigins policy requires Chrome 85 or later.
Close all browser tabs and relaunch the browser.
Verify that your browser applied the new policy by navigating to chrome://policy or edge://policy. The recently added policy should be listed under the Chrome Policies or Microsoft Edge section with the OK status.

Cron Expressions

When updating from v2018.1.x or v2018.2.x to either v2018.4.x or v2019.x, the use of invalid cron expressions in your schedules causes them to stop working. See below examples of incorrect cron syntax, the corrected expression, and its description.

Incorrect Syntax	Corrected Syntax	Description
`0 45/60 09-16 ? * MON-FRI *`	`0 45 09-16 ? * MON-FRI *`	At 45 minutes past the hour, between 09:00 AM and 04:59 PM, Monday through Friday.
`0 30/60 09-15 ? * MON-FRI *`	`0 30 09-15 ? * MON-FRI *`	At 30 minutes past the hour, between 09:00 AM and 03:59 PM, Monday through Friday.
`0 0/120 22-03 ? * MON-SAT *`	`0 0 22-03/2 ? * MON-SAT *`	Every 2 hours, between 10:00 PM and 03:59 AM, Monday through Saturday.