Manual Intervention with parallel step can get stuck in Cancelling state.

[dan-close]

Severity

1 customer reported

Version

2025.3.14320

Latest Version

None

What happened?

When a Manual Intervention step runs in parallel with another step, it can cause the deployment to hang in a Cancelling state in certain situations.

If the deployment is aborted via Manual Intervention or if it is cancelled, it will not complete the cancellation. The deployment can only be cleared from the queue at that point by restarting the Octopus instance.

Reproduction

1. Include a Manual Intervention step in a deployment.
2. Have a Run a Script step that runs in parallel with the Manual Intervention.
3. The script step can do something simple like ping google.com every 5 seconds.
4. Once the Manual Intervention triggers, choose the Abort option.
5. Alternatively, you can cancel the deployment before interacting with the Manual Intervention.
6. Observe that the task will hang in the Cancelling state until you do an instance restart.

Error and Stacktrace

No errors observed

More Information

No response

Workaround

No response