Fix empty assistant message handling in AWS Bedrock Converse API to prevent 400 Bad Request errors #15850
+98
−2
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.
Title
Fix empty assistant message handling in AWS Bedrock Converse API to prevent 400 Bad Request errors
Relevant issues
Pre-Submission checklist
Please complete all items before asking a LiteLLM maintainer to review your PR
tests/litellm/directory, Adding at least 1 test is a hard requirement - see detailsmake test-unitType
🐛 Bug Fix
Changes
Problem
AWS Bedrock Converse API returns a 400 Bad Request error when assistant messages contain empty or whitespace-only text content. The error message is:
This occurs when users pass messages like:
Solution
Modified the
_bedrock_converse_messages_ptfunction inlitellm/litellm_core_utils/prompt_templates/factory.pyto handle empty assistant content by replacing it with a non-empty placeholder text.Key Changes:
".""."Code Changes
Screenshot