Repository navigation
Fix mapped-task retry policy example in tasks docs - #74343
Merged
kaxil merged 1 commit intoOct 6, 2026
Merged
Conversation
The example used `@task.partial(...).expand(...)` as a decorator, which raises `AttributeError: task decorator 'partial' not found`. Show the `@task(retry_policy=...)` + `.expand()` form and the classic operator `.partial(retry_policy=...)` form instead.
vatsrahul1001
approved these changes
Oct 6, 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.
The "Mapped tasks" example under retry policies in the tasks docs does not run:
taskis aTaskDecoratorCollection, sotask.partialis looked up as a provider task decorator and raisesAttributeError: task decorator 'partial' not found. Calling.expand()as a decorator is not a supported pattern either. The example came in with #73027.This replaces it with the two forms that work:
@task(retry_policy=...)followed by.expand(), and.partial(retry_policy=...)on a classic operator. The surrounding prose said the policy is set "via.partial()", which only holds for the classic form, so it now names both.Before
A Dag file containing the documented snippet fails to import:
After
Both new snippets, run in Airflow with a policy that returns FAIL on
ValueErrorand a task withretries=3that raises it for input2. The policy fails map index 1 on its first try, and the other two instances succeed:The log of map index 1 shows the policy decision:
The classic
BashOperator.partial(task_id=..., retry_policy=...).expand(...)form maps three instances:Dag used for the "after" run
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.