Proactively cancel activities on workflow termination and timeout#10047
Draft
Proactively cancel activities on workflow termination and timeout#10047
Conversation
When a workflow is terminated or times out, dispatch cancel commands to workers for in-flight activities that registered a control queue. Previously workers only discovered this passively via heartbeat or NOT_FOUND on completion. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
…dc tests Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
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
1 participant
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
When a workflow is terminated or times out, dispatch cancel commands to workers for in-flight activities that registered a control queue. Extends the mechanism from #9233 to cover forceful workflow close scenarios (including reset, which terminates the old run).
Guarded by EnableCancelActivityWorkerCommand. Disabled.
Why
Previously, workers only discovered workflow termination/timeout passively via heartbeat (
NOT_FOUND) or when completing the activity. If heartbeat isn't enabled, activities run to completion uselessly.How did you test it?
🤖 Generated with Claude Code