We're using the octopus little bit specific way for copy databases from the Live environment to staging, dev test.. etc. including anonymization and related steps. The most important functionality is the parallel processing.
The most important functionality is the parallel processing.
Anyway, the body of PowerShell processing is in our case same.
Just every parallel running task is responsible to process only particular part.
It leads to following configuration:
OctopusBypassDeploymentMutex = $True
and cration following structur in Octopus:

1 Not important starting step

2 Parallel procesing step part 0

2.1 Sub-step 1 of processing part 0 where body of script is {execute_step1 -task 0 -numberOfTasks 10}

...

2.30 Sub-step 30 of processing part 0 where body of script is {execute_step30 -task 0 -numberOfTasks 10}

3 Parallel procesing step part 1

3.1 Sub-step 1 of processing part 1 where body of script is {execute_step1 -task 1 -numberOfTasks 10}

...

3.30 Sub-step 30 of processing part 1 where body of script is {execute_step30 -task 1 -numberOfTasks 10}

4 Parallel procesing step part 2

4.1 Sub-step 1 of processing part 2 where body of script is {execute_step1 -task 2 -numberOfTasks 10}

...

4.30 Sub-step 30 of processing part 2 where body of script is {execute_step30 -task 2 -numberOfTasks 10}

...

4 Parallel procesing step part 9

4.1 Sub-step 1 of processing part 9 where body of script is {execute_step1 -task 9 -numberOfTasks 10}

...

4.30 Sub-step 30 of processing part 9 where body of script is {execute_step30 -task 9 -numberOfTasks 10}

The Octopus is allowing us to configure it this way and it's working fine.
The question is if its possible to configure the process more easy way because in this case we have after a change of any "Sub-step" review and update each of these 9 steps.
I was hoping that this functionality is somehow covered by "Window size" setup in step, but unfortunately, it seems to be the configuration for something else.