Why The X-UIPATH-OrganizationUnitId Changed Automatically?

News Knowledge Base
1

Why does X-UIPATH-OrganizationUnitId change automatically?

Issue Description: Due to X-UIPATH-OrganizationUnitId changing automatically, the previous Orchestrator API calls are not working anymore, and error such as,

  • { "message": "Folder does not exist or the user does not have access to the folder.", "errorCode": 1100, "traceId": "00-d95e3f857c3cbd0de02b05d2a40a3337-6aa03f709c9744cb-00", "resourceIds": null }


Root Cause:

  • If the licensing plan for the Orchestrator account (for example, from Enterprise Trial to Enterprise) is being changed, the FolderId value also change, whereas the FolderKey value remains the same.
  • If the company has moved from an On-Premise Enterprise Orchestrator to a Cloud Orchestrator recently, this causes lately the change in the FolderId. It is not assured that these FolderId will be stable and the parameter unchanged. This working condition may be changed in future product releases.

Resolution:

  • It is recommended to use the X-UIPATH-FolderKey key in the headers section, instead of X-UIPATH-OrganizationUnitId and passing the Folder key value, which is immutable.

Example (the Folder is named "Shared"):

1.png