Publishing new package for a new process but updates old process instead

Hello everyone,

Scenario is: There’s one process that’s already in the orchestrator in a different name. I am publishing a new process now with a new name but instead of creating a new process as V1.0 - it is creating as a new version of the old process. I don’t know why this is happening when the names of the processes/packages are entirely different.

Please help resolving this.

You need to look in the project.json file for the old name and update it.

Of course take a backup (to an entirely different folder structure, I use my desktop) before making any updates.

1 Like

@Aaron_Hubbart Thank you! It worked :slight_smile: