Fix Terminating Pending Orchestration Regression #1288
Draft
+10
−5
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.
When terminating a pending orchestration, I call
MergeEntityAsyncbecause I assume the instance entity already exists. This assumption is incorrect in the case that an orchestration has since been purged after the termination message has been enqueued. This PR adds a check to see if the instance entity exists, and if the execution ID matches that of the termination message's, before attempting to update the entity's status to terminated.Solves #1287