Can't rename duplicate steps when there are multiple duplicates


We have a project which has two sets of steps with duplicate names:

  • Steps 5 and 6 have the same name (say, “install abc”)
  • Steps 9 and 10 have the same name (e.g. “install xyz”)

This project was created about 6 months ago, presumably while we were running a version of Octopus that didn’t have the requirement for unique step names.

We recently upgraded to version 2018.1.3, we’re unable to rename these steps because when we try to rename step 5 or 6 it complains that steps 9 and 10 still have the same name, and when we try to rename step 9 or 10 it complains that steps 5 and 6 still have the same name.

In addition, we’re unable to make any other changes to the project because it complains about both sets of duplicate steps.

We’re currently investigating whether we can get ourselves out of this pickle by making an API call to rename steps 5 and 9 at the same time, but I figured you might want to know about this catch-22 problem.

Note - this also happens in version 2018.3.8 on our lab server.



As an update, we were able to fix this using the API by changing the names of steps 5 and 9 in the same POST so we’re out of the woods for now.

Hi Mike

Thanks for getting in touch! My apologies for the inconvenience caused by this problem.

You are correct, this issue was caused by a new validation rule which we added without a proper data migration.

Data consistency is what we are aiming to improve in this quarter. Hopefully the similar issue will not happen in the future.

Kind regards

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.