AddQueueItem Fails With Folder Does Not Exist Or User Does Not Have Access To Folder

News Knowledge Base
1

Why the Add Queue Item activity fails with error "Folder does not exist or the user does not have access to the folder. Error code 1100." ?

Renaming a few folders causes all our bots to blow up with the message below. I had to revert the changes. Please advice. Throw AssetFailedToLoad Exception: Loading asset xxx failed: Folder does not exist or the user does not have access to the folder. Error code: 1100; Asset

Scenario #1:
Root Cause: The Orchestrator Queue Folder Path provided in the "Folder Path" property of the activity might be wrong.


Resolution:

  1. Make sure that the Orchestrator Queue Folder path provided in the Folder path activity is correct one. This field only supports string values, with / as the separator to indicate subfolders
  2. The Robot user has access to the queue [Check the roles and permissions for the queue] .

Read more on Add Queue Item .

Also, the same error can show up when using the APIs:

When trying to use the Orchestrator API with the given URL (https://cloud.uipath.com/test/DefaultTenant/odata/Queues/UiPathODataSvc.AddQueueItem), the following error is encountered:

{

"message": "Folder does not exist or the user does not have access to the folder.",

"errorCode": 1100,

"traceId": "00-ca6dfc63b10a9741af4aa69e5e2edb92-6bfd8609b74611fc-01",

"resourceIds": null

}

Root Cause: This error occurs when the Folder ID added to the "X-UIPATH-OrganizationUnitId" header is incorrect, resulting in a failure to access the specified folder.


Resolution: Follow these steps,

  1. Open the UiPath Orchestrator with the same user account used to obtain the access token information.
  2. Navigate to the specified folder.
  3. Extract the correct Folder ID from the URL in the address bar of your browser.

Image_2023-04-20_10-48-26.png

  1. After obtaining the correct Folder ID, update the "X-UIPATH-OrganizationUnitId" header with the new ID and try using the API again. This should resolve the error and allow to successfully access the folder.




Scenario #2 :

When a folder is renamed in Orchestrator and the folder name is referenced in projects. One such failure is due to the inability to getAssets from Orchestrator.

Cause/Resolution: The possible cause & resolution of this issue could be as below.
  1. Check getasset in workflow is referencing a folder. It is important to check all part of workflows where getAsset is used and check if folder name is used and update it with new name
  2. If you use an REFramework project, check the config.xls file if there are any assets with the folder path defined. If that is the case, update it with the new folder name.
Learn more on how to use the Get Asset activity.