This exception message indicates that a user object still exists.
Issue description:
This exception has been reported to occur in the following scenarios
Automation Cloud
- A local account or group is deleted from Automation Cloud but not from Orchestrator and the customer tries re-adding this same user object.
- When trying to edit the roles of the user object mentioned above use the 'Assign roles' button.
Standalone
- Account that the user is trying to add is still being referenced by a classic robot in a classic folder.
Resolution:
Automation Cloud
They will need to ensure that said group or user is deleted from both Automation Cloud portal and Orchestrator and then re-added to Orchestrator.
Standalone
They will need to navigate to Tenant -> <Classic Folder Name> -> Robots and remove the robot profile referencing the account.
Note:- Reach out to UiPath product support in case you are not able to find the record of the user that is causing the issue