Loading asset {asset_name} failed: Invalid request!
Issue description:
The concern involves a job commencing as anticipated but failing during the performance of load asset from Orchestrator. The failure occurs due to an error listed as an invalid request.
Error Information:
The error message states "Loading asset {asset_name} failed: Invalid request!"
Troubleshooting Strategy:
To diagnose this problem, gather fiddle traces whilst reproducing the issue via the Knowledge Base. The following error messages might occur during the fiddling process:
- User is not part of partition xxx (tenant Id)
- User provided does not belong in partition xxx( tenant id)
Root Cause:
Close examination of the problem led to the origin - an operation involving DELETE RobotAccount/BulkDelete [partitionGlobalId]. This operation occurs when the client calls the Identity Delete API. As Orchestrator responds to ledger delete events and tries to delete the user, the operation sometimes fails. In this particular situation, deletion of the user from the Orchestrator database was unsuccessful due to a linked trigger.
Resolution:
- Go to the admin portal in Orchestrator and access the audit logs.
- Confirm whether there was a bulk delete or delete request for the bot account.
- Also, refer to admin -> accounts and groups -> robot accounts to ascertain if the bot account is available.
- If there was a delete request and the bot account is missing from robot accounts, go ahead and delete the existing bot.
- Construct a new bot account from the beginning and assign roles in tenant via manage access.
- Finalize the robot setup and settings, designate it to a folder, and then restart the job.
- If nothing helps, get in contact with UiPath Support.