Repository navigation
Child process template steps can become cancelled instead of skipped when run conditions are not met #10239
Description
Severity
Non-blocking
Version
Earliest tried was 2026.2.13434
Latest Version
I could reproduce the problem in the latest build
What happened?
When a deployment process includes a process template with conditional steps and child steps, the first child step belonging to a conditional parent can be marked as cancelled. This happens when the parent step's condition evaluates to true but the child's condition to false. This is a confusing visual indicator, but is non-blocking since the deployment continues successfully.
Reproduction
- Create a process template with one step containing 2+ child actions.
- Set the parent step's condition to Variable with a true expression: #{unless Octopus.Deployment.Error}True#{/unless}
- Set the first child action's condition to Variable with a false expression (unset variable): #{if tplt.tokens.replace.include.files}True#{/if}
- Give a later child action a true/no variable condition.
- Publish the template, reference it from a project via a "Run a Process Template" step.
- Create a release and deploy.
Error and Stacktrace
More Information
No response
Workaround
No response
Activity
lvrbancic commentedon Sep 22, 2026
Additional thing that happens is when the childs first step doesn't have any condition it runs fine and every next one runs fine as well.
So the bug here is only acting if the first child action's condition to Variable with a false expression (unset variable): #{if tplt.tokens.replace.include.files}True#{/if}