Failure-of-set-asset-during-automation-after-upgrading-uipath-orchestrator-you-are-not-authorized-error-code-0

Failure of "Set Asset" During Automation After Upgrading UiPath Orchestrator - "You are not authorized error code:0"

Issue Description:


After upgrading to a newer version of UiPath Orchestrator, users may encounter an error when attempting to use the "Set Asset" activity in their automation processes. The specific error message displayed is: “You are not authorized error code:0.” This issue prevents the activity from successfully setting the asset.


Root Cause:


The error arises due to insufficient permissions assigned to the robot user. The "Set Asset" activity requires specific permissions to access and modify asset values. Following an upgrade, there may be changes in permission structures or authentication contexts, resulting in missing or misconfigured permissions at both the tenant and folder levels.



Resolution:

1. Verify Tenant-Level Permissions:

  • Confirm that the roles assigned to robot users include permissions for managing assets. Specifically, ensure that the roles have:
    • View Assets
    • Edit Assets
    • Create Assets (if the process involves creating new assets)

2. Check Folder-Level Permissions:

  • Navigate to the specific folder containing the asset. Verify that the robot user is assigned a role that includes permissions to manage assets within that folder. The permissions should include:
    • View Assets
    • Edit Assets
    • Create Assets (if applicable)

3. Assign or Modify Roles:

  • If the necessary permissions are missing, create or modify a role to include the required permissions and assign this role to the robot user in the specific folder.

4. Test the Automation Process:

  • After updating the permissions, conduct a test of the automation process to confirm that the "Set Asset" activity can successfully modify the asset without triggering the "You are not authorized error code:0" error.

Conclusion:

The “You are not authorized error code:0” error encountered during the "Set Asset" activity is primarily due to missing or incorrect permissions for the robot user. By verifying and correctly assigning permissions at both tenant and folder levels, the issue can be resolved, allowing the automation process to execute as intended.