Fix lambda executor max attempts config#60666
Merged
o-nikolas merged 2 commits intoapache:mainfrom Jan 17, 2026
Merged
Conversation
The documentation and even most of the code properly refers to the config as `max_invoke_attempts` but the config name itself (which was read from Airflow config/env) was using the wrong config name (`max_run_task_attempts` which comes from the ECS executor)
boring-cyborg
bot
added
area:providers
provider:amazon
vincbeck
approved these changes
Jan 16, 2026
jason810496
pushed a commit
to jason810496/airflow
that referenced
this pull request
Jan 22, 2026
* Fix lambda executor max attempts config The documentation and even most of the code properly refers to the config as `max_invoke_attempts` but the config name itself (which was read from Airflow config/env) was using the wrong config name (`max_run_task_attempts` which comes from the ECS executor) * Update changelog for the breaking change
85 tasks
shreyas-dev
pushed a commit
to shreyas-dev/airflow
that referenced
this pull request
Jan 29, 2026
* Fix lambda executor max attempts config The documentation and even most of the code properly refers to the config as `max_invoke_attempts` but the config name itself (which was read from Airflow config/env) was using the wrong config name (`max_run_task_attempts` which comes from the ECS executor) * Update changelog for the breaking change
jhgoebbert
pushed a commit
to jhgoebbert/airflow_Owen-CH-Leung
that referenced
this pull request
Feb 8, 2026
* Fix lambda executor max attempts config The documentation and even most of the code properly refers to the config as `max_invoke_attempts` but the config name itself (which was read from Airflow config/env) was using the wrong config name (`max_run_task_attempts` which comes from the ECS executor) * Update changelog for the breaking change
choo121600
pushed a commit
to choo121600/airflow
that referenced
this pull request
Feb 22, 2026
* Fix lambda executor max attempts config The documentation and even most of the code properly refers to the config as `max_invoke_attempts` but the config name itself (which was read from Airflow config/env) was using the wrong config name (`max_run_task_attempts` which comes from the ECS executor) * Update changelog for the breaking change
Subham-KRLX
pushed a commit
to Subham-KRLX/airflow
that referenced
this pull request
Mar 4, 2026
* Fix lambda executor max attempts config The documentation and even most of the code properly refers to the config as `max_invoke_attempts` but the config name itself (which was read from Airflow config/env) was using the wrong config name (`max_run_task_attempts` which comes from the ECS executor) * Update changelog for the breaking change
Ankurdeewan
pushed a commit
to Ankurdeewan/airflow
that referenced
this pull request
Mar 15, 2026
* Fix lambda executor max attempts config The documentation and even most of the code properly refers to the config as `max_invoke_attempts` but the config name itself (which was read from Airflow config/env) was using the wrong config name (`max_run_task_attempts` which comes from the ECS executor) * Update changelog for the breaking change
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
2 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 documentation and even most of the code properly refers to the config as
max_invoke_attemptsbut the config name itself (which was read from Airflow config/env) was using the wrong config name (max_run_task_attemptswhich comes from the ECS executor)Note: The Lambda Executor is still in alpha/experimental mode. So we are able to make this breaking change. However, this config is not often used, so it should be fairly low impact as well.
Was generative AI tooling used to co-author this PR?
{pr_number}.significant.rstor{issue_number}.significant.rst, in airflow-core/newsfragments.