Fix AWS Lambda executor error handling for DLQ vs task failures #53990
Conversation
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
boring-cyborg
bot
added
area:providers
provider:amazon
o-nikolas
reviewed
Jul 31, 2025
providers/amazon/src/airflow/providers/amazon/aws/executors/aws_lambda/lambda_executor.py
Outdated
Show resolved
Hide resolved
providers/amazon/src/airflow/providers/amazon/aws/executors/aws_lambda/lambda_executor.py
Outdated
Show resolved
Hide resolved
o-nikolas
approved these changes
Jul 31, 2025
providers/amazon/src/airflow/providers/amazon/aws/executors/aws_lambda/lambda_executor.py
Show resolved
Hide resolved
40 tasks
ferruzzi
pushed a commit
to aws-mwaa/upstream-to-airflow
that referenced
this pull request
Aug 7, 2025
…he#53990) Enhanced error handling in the AWS Lambda executor to better distinguish between Lambda service failures (DLQ) and task execution failures. Added check to properly identify DLQ failures and updated error messages to clearly indicate whether the failure was at the Lambda service level (timeout/crash/memory) or during task execution.
fweilun
pushed a commit
to fweilun/airflow
that referenced
this pull request
Aug 11, 2025
…he#53990) Enhanced error handling in the AWS Lambda executor to better distinguish between Lambda service failures (DLQ) and task execution failures. Added check to properly identify DLQ failures and updated error messages to clearly indicate whether the failure was at the Lambda service level (timeout/crash/memory) or during task execution.
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.
Enhanced error handling in the AWS Lambda executor to better distinguish between Lambda service failures (DLQ) and task execution failures.
Added check to properly identify DLQ failures and updated error messages to clearly indicate whether the failure was at the Lambda service level (timeout/crash/memory) or during task execution.
Previously, logging failures from the DLQ contained the incorrect field
return_codeinstead ofcommandwhich is located in the DLQ message body.^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rstor{issue_number}.significant.rst, in airflow-core/newsfragments.