Failed to run the command. ``Service: orchestrator not found in Organization: *** Tenant: ***`` The Orchestrator command ``https://cloud.uipath.com/***/***/***/odata/Folders?%24filter=FullyQualifiedName%20eq%20%27***%27`` failed with status code NotFound

Help Orchestrator
1

Good day

I am trying to run a UiPath job via azure pipelines but I’m getting the following error

Failed to run the command. Service: orchestrator not found in Organization: *** Tenant: *** The Orchestrator command https://cloud.uipath.com/***/***/***/odata/Folders?%24filter=FullyQualifiedName%20eq%20%27***%27 failed with status code NotFound.

Can someone please assist?

2

Hey @rolandig
This error typically happens due to misconfiguration in your Orchestrator URL, organization name, or tenant name in your Azure DevOps pipeline or UiPath CLI/API settings.

UiPath Cloud URLs follow this pattern:

bash

CopyEdit

https://cloud.uipath.com/<organization>/<tenant>/...

But if one part is wrong or missing, you’ll get 404 Not Found.

Checklist to Fix the Issue

  1. Double-check Your Orchestrator URL

Log in to https://cloud.uipath.com, and once you’re in your portal, the browser will show something like:

https://cloud.uipath.com/myOrgName/myTenantName

Make sure you’re using:

  • The correct organization name (myOrgName)
  • The correct tenant name (myTenantName)
  • No typos or placeholder values left in your YAML or CLI config
  1. Make Sure the Tenant is Linked to a Modern Folder

If you’re using a modern folder, the odata/Folders query must be looking in the correct tenant/folder structure.

Ensure:

  • The folder exists
  • It’s accessible to the robot/user you’re using for the job
  • You have permissions to view folders via API
  1. Use the Correct UiPath CLI or Integration Settings

If using the UiPath CLI (uipcli) or the Azure DevOps UiPath Extension, ensure:

  • You’ve set the correct Orchestrator URL
  • You’re passing the correct --cloudOrchestratorUrl, --account, and --tenant
1 Like
3

Thank you! I’m not getting that error anymore, I did not add the tenant in the URL previously so I think that resolved the issue

1 Like
4

Hey @rolandig if the error is resolved kindly close this thread by marking as solution.

cheers

1 Like
5

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.