Fix example_mwaa_serverless system test race condition with stop_workflow_run#67578
Merged
Merged
Conversation
…flow_run The stop_workflow_run task was failing with a ValidationException because the workflow run completed before the stop command could be issued. This was particularly problematic on high-latency executors (e.g., ECS) where task launch overhead (~90s) gave the workflow enough time to finish. The fix introduces a second workflow definition (stoppable_workflow.yaml) that sensors for a non-existent S3 key, keeping the workflow running indefinitely until explicitly stopped.
boring-cyborg
Bot
added
area:providers
provider:amazon
eladkal
approved these changes
May 26, 2026
vincbeck
approved these changes
May 27, 2026
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
3 participants
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.
The stop_workflow_run task was failing with a ValidationException because the workflow run completed before the stop command could be issued. This was particularly problematic on high-latency executors (e.g., ECS) where task launch overhead (~90s) gave the workflow enough time to finish.
The fix introduces a second workflow definition (stoppable_workflow.yaml) that sensors for a non-existent S3 key, keeping the workflow running indefinitely until explicitly stopped.
Ran the system test locally and it passed
Was generative AI tooling used to co-author this PR?
{pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.