Failed to run the command. Could not connect to Cloud Orchestrator: UiPath Orchestrator, Account Name For App: , Application Id: ***, Application Scope(s): ***, Tenant: , Organization Unit: Shared.
Please make sure that the provided URL (UiPath) is correct, available from your build agent, and not blocked by a firewall.
If the Orchestrator is using a self-signed SSL certificate, make sure that the build agent trusts it. Ensure that all the steps at Self-signed certificates were correctly followed when creating the certificate.
So is it because of mismtach in email IDs of azure devops and Orchestrator Account?
I see this topic is old but I just ran into this issue yesterday and have yet to figure this out. Did you ever get this resolved @pdubey? If so, how did you fix it? Thanks.
The only unfortunate factor is that the change I made was switching from External Application (OAuth) to Token-Based. I’ll be submitting a ticket with UiPath to see about being able to use the External Application method in the future.
Thanks for this. I had the same issue, specifically with the Manage Assets step. I was using OAuth successfully for the main steps but Manage Assets couldn’t connect to Orchestrator for some reason so I had to change the service connection to use token-based (which then worked successfully).
I might raise this as a bug (with Manage Assets) specifically as it seems some of the steps have been updated to use OAuth but not all of them.