QNA Bot with bedrock knowledgebase and connect feature.

[dangollayan]

Describe the bug
The bot sometimes returns a blank response when using the Bedrock knowledge base as a fallback feature.

To Reproduce
Ask the bot a question that triggers the Bedrock knowledge base fallback feature.

Expected behavior
The bot should display the results retrieved from the Bedrock knowledge base.

Please complete the following information about the solution:

• [v6.1.1] Version:

• [ap-southeast-2] Region

• [No] Was the solution modified from the version published on this repository?

• [N/A] If the answer to the previous question was yes, are the changes available on GitHub?

• [Yes ] Have you checked your service quotas for the services this solution uses?

• [No] Were there any errors in the CloudWatch Logs?

Screenshots
Sample screenshot of empty response

Logs of empty response:

Connect flow I used:

Additional context
Based on testing and log analysis, the response is blank if the Bedrock knowledge base processing time exceeds 6-7 seconds.

[fhoueto-amz]

Thanks. We will revert back.

[abhirpat]

Hi @dangollayan, thank you for reporting this. To help further investigate it -

1. You mentioned you see response blank in connect. Could you please try comparing in QnABot's chat client? Does it show blank as well?
2. Also, in your logs, could you also please provide an expansive screenshot of last line that says "INFO final:". It's the final response that is sent to clients that we need to look at.
3. Have you checked logs from connect chat side to see if there any errors? You can also try to see browser console logs in chrome developer tools and network logs.

[abhirpat]

Hi @dangollayan wanted to check-in to see if you had a chance to see my previous message.

[dangollayan]

Hi @dangollayan wanted to check-in to see if you had a chance to see my previous message.

Hi, sorry for the late response and thank you for looking out for our problem

1. Yes, it shows blank also
2. in the screenshot I sent, in the cloudwatch logs, there's "final:" part
3. I'll get back to you ASAP