Question
Banco Múltiple Bhd León SA
DO
Last activity: 18 Dec 2025 14:31 EST
Failed to retreive binary package from Pega Robot Manager
Hello,
We are getting an error when we tried to connect VM to Pega Robot Manager, the Repository have been fully set, the Communication has been established the Robot successfully registered to Robot manager but once it call the Robot Manager to retrive the binary package we received and error saying "Theres no deployable package file" or "WebCacheService.DownloadFileFromRobotManager : unexpected server status code while getting etag from server".
We already tried:
- Delete Operator ID from Pega
- Uninstall and install again Pega Robot Runtime
- Tried the same package in another VM
- We already configured 5 VM without any further issues from other Workgroups and binaries packages
- Delete pegasystems folder on %appdata%
- Load the project manually also works fine
Pega Robot Runtime Version 22.1.48
Accepted Solution
Banco Múltiple Bhd León SA
DO
HCA Healthcare
US
Your VM is reaching Robot Manager and the robot is registering fine, but the download of the assigned package binary is failing on the Robot Manager side with an HTTP 500 while trying to read the ETag for the binary endpoint, so the runtime never gets a file to save locally.
In Robot Manager, open that exact package/version that is assigned and confirm it has a deployable runtime package uploaded (not just the project), because the runtime log also shows No package from server.
Rebuild and republish the package as a brand-new version (new build) and reassign that new version to the workgroup/robot, since a corrupted or incomplete artifact commonly causes this exact symptom.
If you use a proxy/WAF, make sure it allows HEAD/GET to /prweb/api/robotics/v2/packages/binary/... and does not strip ETag/If-None-Match headers, because the failure is happening during the ETag fetch step.
Also verify the Robot Manager repository/storage is healthy (disk/S3 permissions/connectivity) and clear server-side caches or restart the Robot Manager service/nodes after republishing.
On the VM, fully remove the local cached package file under AppData\Local\Pegasystems\22.1\Projects\... and retry after the new package version is assigned, so it cannot reuse a bad partial download.
Your VM is reaching Robot Manager and the robot is registering fine, but the download of the assigned package binary is failing on the Robot Manager side with an HTTP 500 while trying to read the ETag for the binary endpoint, so the runtime never gets a file to save locally.
In Robot Manager, open that exact package/version that is assigned and confirm it has a deployable runtime package uploaded (not just the project), because the runtime log also shows No package from server.
Rebuild and republish the package as a brand-new version (new build) and reassign that new version to the workgroup/robot, since a corrupted or incomplete artifact commonly causes this exact symptom.
If you use a proxy/WAF, make sure it allows HEAD/GET to /prweb/api/robotics/v2/packages/binary/... and does not strip ETag/If-None-Match headers, because the failure is happening during the ETag fetch step.
Also verify the Robot Manager repository/storage is healthy (disk/S3 permissions/connectivity) and clear server-side caches or restart the Robot Manager service/nodes after republishing.
On the VM, fully remove the local cached package file under AppData\Local\Pegasystems\22.1\Projects\... and retry after the new package version is assigned, so it cannot reuse a bad partial download.
If other packages/workgroups work but only this one fails, treat it as a package artifact issue first (rebuild/reupload) rather than a VM/runtime install issue.
Banco Múltiple Bhd León SA
DO
We confirmed a deployable package was available, also we tried another package on that VM and works just fine, we used the native repository: pegacloudfilestorage, we rebuild and redeployed the package a couple of times changing ID and name without effect as a matter of fact this robot was migrated from version 19.1.3 to version 22.1.48 could be possible that migration corrupted any XML or file that is preventing to correctly connect and retrieve the package?
Pegasystems Inc.
GB
Hi @JoséSamuelM ,
The error seems to indicate that the binary file for the package ID 7642322E6E43031 and version 2.0 doesn't exists in the storage.
Did you check the actual file is there?
You mentioned that you deployed a new version of the package, did you update the assignment to the robot and tested?
If you are still struggling with this, you can open an INC and we could have a call to go through it.
Accepted Solution
Banco Múltiple Bhd León SA
DO
@Angel Hermira We dig deeper and find the issue the project Id did not have all the letter capitals so when we deploy and tried to connect a VM the API call trying to connect to RM set the ID completely in capital therefore none match.
To solve this, we only rename the project ID to capitals and delete the old one from robot manager and once we tried again we succesfully connect the VM.
@Angel Hermira We dig deeper and find the issue the project Id did not have all the letter capitals so when we deploy and tried to connect a VM the API call trying to connect to RM set the ID completely in capital therefore none match.
To solve this, we only rename the project ID to capitals and delete the old one from robot manager and once we tried again we succesfully connect the VM.