- Newest
- Most votes
- Most comments
ℹ️ This type of error usually occurs when the input parameters or configurations do not meet the expected format or when there is a misconfiguration in handling the response
💡 Since Bedrock Agent uses a default parser lambda function that isn't visible to you, the best approach to debug issues is to ensure that the data sent to the agent conforms exactly to the expected format. Add extensive logging before the API call to verify that all parameters are correct and complete.
Check the output format from any Lambda functions, it needs to be in a specific format for the default parser to be able to parse it: https://docs.aws.amazon.com/bedrock/latest/userguide/lambda-parser.html
Hi @Gillian, we are not using any Parser Lambda function. After going through the link that you have shared, i have understood that Bedrock Agent uses a default parser lambda function which is not visible to us. Can you provide a way to debug the issues in that? Since we don't prefer to use a custom parser lambda function.
Can you give me more details on the Agent? Does it work if you invoke it through the "Test Agent" on the Agent page on the AWS Console? It provides a full set of traces so you can easily identify any issues.
Relevant content
- Accepted Answerasked 10 months ago
- Accepted Answerasked 2 years ago
- AWS OFFICIALUpdated 5 months ago
Hi @Gillian, we are not using any Parser Lambda function. After going through the link that you have shared, i have understood that Bedrock Agent uses a default parser lambda function which is not visible to us. Can you provide a way to debug the issues in that? Since we don't prefer to use a custom parser lambda function.