Update manual intervention docs#3173
Merged
Merged
Conversation
…d when server task cap spot is freed up.
|
Pull request environment is available at https://stoctodocspr3173.z22.web.core.windows.net. You can view the ephemeral environment status in Octopus Deploy. This environment will be automatically deprovisioned when the pull request is closed, or after 7 days of inactivity. |
lucyjspence
approved these changes
May 25, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Update manual intervention docs with info on when pausing happens and when server task cap spot is freed up.
Related to: OctopusDeploy/Issues#10041
Which was implemented by: https://github.com/OctopusDeploy/OctopusDeploy/pull/41091
We have changed Octopus Server to allow manual interventions to be used as child steps outside of rolling deployments.
This has implications for when a server task is paused (freeing a spot in the task cap), and when an execution merely halts waiting for manual intervention without actually pausing the overall server task.
Previously this level of detail was not covered in the manual intervention docs.
This PR updates them to cover it.