Closed abilash44 closed 5 months ago
Hi @abilash44 - unfortunately, the debug does not appear if there is an unhandled exception on the backend. The place you want to look for errors with the chat client is in the fulfillment lambda's log: https://us-east-1.console.aws.amazon.com/cloudwatch/home?region=us-east-1#logsV2:log-groups$3FlogGroupNameFilter$3Dfulfillment.
We're actively working on this already, so we will keep this issue open for updates.
Hi @abilash44 - could you please try testing this in latest QnaBot version 5.5.0? You can deploy QnaBot using template available in https://aws.amazon.com/solutions/implementations/qnabot-on-aws/. If issues persist, please provide errors in fulfillment lambda logs as mentioned above.
Looking forward to hearing from you.
Hi @abilash44, we haven't heard from so we are going to archive the case. As next step, I'd recommend trying out latest release v6.0.0 as we have made improvements to error message in designer and chat client. For chat client, I'd recommend to enable setting ENABLE_DEBUG_RESPONSES
in the designer.
For 6.0.0 release, please refer to CHANGELOG for additional details about this release. Thank You!
If you still seen an issue, please create an example question > export > attach it as json for us to replicate the issue.
Is your feature request related to a problem? Please describe. I made a mistake of using the data id instead of the index id for the kendra index.
Describe the feature you'd like
Additional context I just went around in circles for a few hours creating and deleting a dozen stacks. lol.