Clarify semantic of cancel wf commands #849
Merged
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.
What was changed
RequestCancelExternalWorkflowExecution
command indicating thatCancelChildWorkflowExecution
should be prefered for cancellation of child workflows, and removed thechild_workflow_id
target on the former to avoid confusion.Why
CancelUnstartedChildWorkflowExecution
command might fail if Workflow tries to cancel child workflow before getting notified of start event #331, we simplified child workflow cancellation command so that lang would simply request cancellation of the child workflow, and core would decide either to actually emit a cancellation command to the server. However,RequestCancelExternalWorkflowExecution.target.child_workflow_id
has not been removed, and no comment had been added, resulting in some confusion as to which API should be used in new code.