Failed To Download Package 'xxx' From Feed 'cloud_orchestrator_feed'. Response Status Code Does Not Indicate Success: 403 (Forbidden)

News Knowledge Base
1

Error fix for " Failed to download package 'xxx' from feed 'orchestrator_feed'. Response status code does not indicate success: 403 (forbidden) " .

The error 'failed to download package (xxx) from feed (Orchestrator feed xxx). Response status code does not indicate success: 403 (forbidden)' is related to a permissions issue when trying to download a package from the Orchestrator.


Root Cause: This occurs when the Robot has no access to the feed listed in the error.

image.png



Resolution:
It is necessary to make sure that the specific user or group for which the Robot has been provisioned has the necessary permissions in Orchestrator to access, download, and execute the package.

  • In Orchestrator, go to Users, then Roles, and check the permissions for the specific role assigned to the Robot. Ensure that the Robot has the necessary "Read" and "Execute" permissions related to Packages, Processes, Jobs, and Environment.
    • Usually, assigning the Roles 'Robot', 'Automation User' and 'Allow to be Automation User' should help solve the issue as these roles have the necessary permissions mentioned above.

Also, launching Assistant as Administrator in such cases can help solve the issue because the administrator level permissions may have been necessary for certain actions that the robot needs to perform, as well as not having restrictions to download packages from the Orchestrator feed. To avoid launching assistant with administrator privileges the following can be checked:

  • There might be varying user profile configurations or policies for non-administrator users that could restrict downloading packages from the Orchestrator feed. Check if there are any specific user policies or profile restrictions in place.
  • It is possible that the proxy settings for the non-administrator user are misconfigured or different from the administrator user's settings. Verify the proxy settings and ensure they are correctly set up for the non-administrator user.
  • Although not directly related to the Orchestrator feed, verify the folder permissions where the packages are downloaded and executed on the Robot machine. Make sure the non-administrator user has proper read and write access to those locations.