How do I deploy an automation to a same robot package version?

General
, , ,
1

It is in the title. I know we get the message “Failed to upload deployment package file to server. Package xxx version yyy already exists.” when we try to deploy to a same robot package version. But is there a way to get that done? I tried removing the package version on the package server, the Platform, and Robot Manager, but I still get that message. I feel that there should be a way to do that, as people may mess up the versions and want to start over or clean things up.

2

Hello,

Pega facilitates the numbering of deployed versions, which, to my best knowledge, is immutable. That ensures rollback capabilities and the general reliability of the packages deployed to the system. In other words, the package versioning works like a version control system that keeps a record of each deployment, and that’s the ‘per design’ behavior.

I’m not sure what scenario you are working with, but I believe that if there’s a mistake, you can deploy the new minor package version (increment version) that fixes the bug and use it in Pega Robot Manager. If you want to start over completely, you need to change the package name, which would restart the version numbering.

Best regards,

Joanna

3

Techincally you can redeploy the same version, but you must first delete the existing entries associated with the package from the following classes, and also remove the binaries from the package server.

Data-Robotic-AutomationPackage
Data-Robotic-AutomationPackage-Version
Data-Robotic-AutomationPackage-Version-Config
Link-Association

I assume that you are missing the final class instances, which is causing the error message mentioned above

4

Thanks for the suggestions, @RanjithK8179. However, I tried all that and still get that error message. Do you have any other insights?

5

@AnB18593 Try tracing the below activity during the deployment you can see what’s causing the issue and why. Based on the error message there are still some instances that relates to your package in Link-Association class (“Package xxx version yyy already exists” error message comes when there is a etag already exists). Make sure you are using same operator for deploying and tracing, if it is different then you have to trace the API referencing the activity

**pzPushPackageBinariesToRepository
**

1 Like