Fix SageMakerUnifiedStudioNotebookOperator workflow_name under MWAA Serverless - #72335
Open
qaziashikin wants to merge 1 commit into
Open
Fix SageMakerUnifiedStudioNotebookOperator workflow_name under MWAA Serverless#72335qaziashikin wants to merge 1 commit into
qaziashikin wants to merge 1 commit into
Conversation
reganbaum
approved these changes
Aug 31, 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
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.
Description
Under MWAA Serverless (Overdrive),
dag_idis overwritten with a per-execution UUID fortenant isolation, so the operator was passing the execution UUID as
workflow_nametoStartNotebookRuninstead of the actual workflow name. This breaks the SMUS UI's abilityto link a notebook run back to the workflow that triggered it.
MWAA Serverless now injects the workflow name as a DAG param under the key
mwaa_serverless_workflow_id. Read from that param when set, fall back tocontext["dag"].dag_idfor standard SMUS Workflows and open-source Airflow.Was generative AI tooling used to co-author this PR?
Claude Opus 4.7
Testing
Ran system test:
{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.