Bot Fails to Download Package; Encounter Error NU1101 (was working fine earlier and services are whitelisted)

When tried to install a new package on the VM using an untended job with bot account, the job fails with NU1101: unable to find package and No packages exist with this Id in sources.

Issue description:

A situation has arisen where the bot is unable to successfully download a package. This activity is followed by the occurrence of an error coded as NU1101.

Error Details:

The bot faces a UiPath.CoreIpc.RemoteException which shows the failure to install package "XXX". Following this, a further UiPath.CoreIpc.RemoteException appears, reading "NU1101: Unable to find package "XXX". No package with this id exists in source(s): "Orchestrator Feed".

PackageSourceMapping is enabled, the following sources were not considered: Connect, https://pkgs.dev.azure.com/uipath/PublicFeeds/_packaging/UiPath-Official/nuget/v3/index.json, Local, nuget.org, Official.

Root Cause:

The root cause of this issue was traced back to an operation related to DELETE RobotAccount/BulkDelete [partitionGlobalId]. Here, the Identity Delete API was called by the client. When Orchestrator reacts to ledger delete events and attempts to delete the user, this operation occasionally fails. In this instance, the user could not be deleted in the Orchestrator database due to an attached trigger.

Resolution:

  1. Begin resolution by referring to the Knowledge Base for troubleshooting the NU1101 error code.
  2. If the error persists, access the audit logs from the admin portal in the Orchestrator.
  3. Verify whether a bulk delete or delete call was requested for the bot account.
  4. Also, check if the bot account is available under admin -> accounts and groups -> robot accounts
  5. If such a request has been made, proceed with deleting the existing bot and unable to find the bot account under robot accounts.
  6. Recreate a new bot account from scratch and assign roles in tenant through manage access.
  7. Complete the robot setup and settings, assign it to a folder, and then restart the job.