Include Bedrock ingestion job failure reasons in the error messages - #71124
Open
ferruzzi wants to merge 1 commit into
Open
Include Bedrock ingestion job failure reasons in the error messages#71124ferruzzi wants to merge 1 commit into
ferruzzi wants to merge 1 commit into
Conversation
boring-cyborg
Bot
added
area:providers
provider:amazon
ferruzzi
force-pushed
the
ferruzzi/system-tests/bedrock-rag-error-msg
branch
from
August 4, 2026 19:29
b3e5b2d to
d81b070
Compare
ferruzzi
force-pushed
the
ferruzzi/system-tests/bedrock-rag-error-msg
branch
from
August 5, 2026 22:10
d81b070 to
5048aae
Compare
ramitkataria
approved these changes
Aug 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
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.
Trying to troubleshoot a flaky system test and I noticed we are swallowing the actual failure reasons here. This PR adds the failure messages back into the exception log and adds tests to prevent regression.
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.