Octopus Upgrade to V4.X

Hi Team,

This is follow-up request that has been created after the ticket - 65657(https://help.octopusdeploy.com/discussions/problems/65657). We are currently using Octopus 3.15.7 and we came across an issue while updating the step template and it turns out to be a open bug in that specific version (https://github.com/OctopusDeploy/Issues/issues/3674)

After we got the update from your team in my previous ticket, we are planning to upgrade our Octopus version to 4.X

I would like to know few more details about the OD upgrade to 4x.

As the latest version of OD is 4.1.4, before upgrading to this version, I would like to know is there any open defects reported in 4.1.X versions and where I can see those details?

Moreover, I could see there were lot of minor releases done on 4.x version (4.0 - 4.1.4), which is the most stable version that you prefer and is there any way we can check that in any of your portals?

Feedbacks are really appreciated.

Thanks in advance.


Hi Karthikeyan,

Thanks for getting in touch! I’m sorry you’re hitting this issue when updating your step template, but happy to hear you found the available fix for it.

We report all issues on a public GitHub repository, which you can refer to here.

We always recommend going to the latest version available as it will contain the most features, fixes and enhancements (i.e. it will the most stable version). You can refer to all of our release notes (including breaking changes) between each individual version on our website, where you can compare between two specific patch versions. For all release notes between versions 3.15.7 and 4.1.5, you can find that information here. :slight_smile:

Upgrading to 4.x can be done following the same process as you would when upgrading to 3.x. Feel free to refer to our upgrading documentation page.

I hope this helps! Let me know if you have any further questions going forward.

Kind regards,


Hello Kenny,

Thanks for the detailed information you’ve provided! Really helpful :slight_smile:

I would like know one more thing related to the breaking change that is stated in 4.0

As stated in the above link, I just need to clarify few things,

  1. Can we override the Octopus.Action.MaxParallelism variable to require number? Because in the above link, you’ve mentioned overriding the variable might lead some errors.

  2. Is this number specific to a Server Task? Like if I trigger a deployment (from a single project) to 2 environments at a same time, each environment deployment will deploy in 7-8 tentacles. So for those 2 deployments, there will be 16+ tentacles . So do I need to override the above stated variable to 20? Might be silly, just need to clarify :slight_smile: Never used this variable before!!!

Thanks in advance for your help!!


Hi Karthikeyan,

Thanks for following up, and you’re very welcome! You can overwrite either of these variables by defining them as project variables with the value that you want. There are actually two variables here: Octopus.Action.MaxParallelism and Octopus.Acquire.MaxParallelism. It’s the second one (..Acquire..) that can affect retention policy. We don’t recommend adjusting this one, but it doesn’t sound like that’s your intention.

You can also adjust Octopus.Action.MaxParallelism, which controls how many machines will be deployed to at once (it now defaults to 10). Increasing this value can potentially have negative performance impacts, so you should monitory your server CPU, memory, etc. after increasing it.

The answer to your 2nd question is yes, this number is specific to a server task. It is per deployment, so if the value is set to 10 (the default), then each deployment will deploy to that many machines concurrently.

I hope this helps! Don’t hesitate to reach out if you have any further questions going forward.

Best regards,


Thanks a lot Kenny for the detailed explanation!!

Appreciate your support in this.