Properly handle uncaught child/activity cancel during workflow cancel #71
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
When a workflow cancel has ever been requested (even if it was a long time ago), we unwrap any activity or child workflow cancel error to be treated as a workflow error.
Why?
When not doing this, the workflow will be considered "failed" with an activity or child error even on uncaught cancel. The downside is that the workflow will be considered cancelled if, say, you disregarded a cancel a long time ago but then way later chose to manually cancel an activity and bubbled that error out. There is no good way to handle this rare situation.
Checklist