Deployments will fail if you change the lifecycle mid-deploymnet

[michelle-luana]

Severity

One customer impacted

Version

2025.1

Latest Version

I could reproduce the problem in the latest build

What happened?

Customer has multiple lifecycles used to specify a combination of environments, in this case environments appear to be used similarly to how we intend tenants to be used.
After deploying to one of these lifecycles but before all deployments had completed, the lifecycle in the project process was changed.
This was a bulk deployment to 100 environments, the deployments still queued after the lifecycle was updated become invalid because the newly changed lifecycle doesn't have the environment(s) that it's trying to deploy to.

Reproduction

1. Create 2 lifecycle phases, each having 1 phase and many environments for that phase. Note that each lifecycle/phase had unique environments.
2. Create a bulk deployment, to all of the environments applicable.
3. Go to deployment process and change the lifecycle for that project
4. You should be able to observe the rest of the deployments that are queued up failing with the error message above.

This is not how we anticipate Octopus Deploy being used, and the resulting behavior is expected. We do not consider this a bug as such but are creating the issue so we can monitor it in case other customers are running into similar issues.