Fix Terminating Pending Orchestrations #1256
Merged
Conversation
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
added 2 commits
October 21, 2025 14:46
andystaples
approved these changes
Oct 21, 2025
sophiatev
deleted the
stevosyan/fix-terminating-scheduled-orchestrations
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Currently, if a user attempts to terminate a pending orchestration, nothing happens and the orchestration still starts once the
ExecutionStartedEventis picked up from the control queue. This PR enables terminating pending orchestrations in the Azure Storage backend by checking for this special case inLockNextTaskOrchestrationWorkItemAsync, and updating the status in storage to "Terminated" if it is detected.Fixes #1255