Octopus 2.4: Step template parameter set to custom variable InstallationDirectoryPath not working in child step


I have set up a script module, a template step that calls a function within the script module (working).
On the step template I have set up a few parameters, one of them is set to the following:

#{Octopus.Action[Campaign Processor].Output.Package.InstallationDirectoryPath}

I have set the following variables to “True”; “OctopusPrintEvaluatedVariables” and “OctopusPrintVariables”.

I have a process step set up that deploys a NuGet package.
The child process step calls the step template I created (script module is enabled for the project)

The step parameter value set to built in custom variable above is not being set.
(However, the parent step is the “Campaign Processor” step).

Any ideas why I am not able to get the installed directory path of the parent NuGet deploy step?

Kind Regards,

Works if I change the child step to be the next step in the process.
I’m guessing this is a bug with the behaviour of the child step execution, or is this by design of rolling deployments?