I have been testing my KB in the QnA Maker Portal using the test chatbot and it doesn’t work as expected with follow-up prompts. I have documented this in a question on Stackoverflow here: https://stackoverflow.com/questions/56966147/qna-maker-knowledge-base-returning-no-good-match-found-in-kb-for-follow-up-pro
The test chatbot returns different question/answer pairs than the ones I have configured in the KB. I have tested the issue directly with the API and it works as expected, so believe this is an issue with the test chatbot
⚠Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
@seanbetts Thanks for your comment. We are actively investigating and will get back to you shortly.
Thank you - appreciate you looking at this. I’m also having the same problems with the question/answer pairs in my chatbot so don’t know if that’s related or not as I’d assume that would use the API?
@seanbetts - Thank you for your patience. Looking into a proper answer. #in-progress
@diberry any progress on this yet? Let me know if there's any testing etc. I can do to help. Thanks
@seanbetts The service team would like to investigate. Can you log into the QnA Maker portal, select Feedback in the top nav bar, add your SO link and question as well as your app id and resource name?
Thanks diberry - I’ve just sent the feedback as requested.
@diberry I submitted the feedback as requested a couple of days ago but haven't heard anything back?
@seanbetts - thanks for letting me know - I'll see if they can take a look.
Thanks @diberry, appreciate it
@seanbetts The service team will look at this in the next day or 2.
@diberry perfect, thank you for checking for me
@seanbetts @tulasim88 Did this get resolved with the service team?
Hi @diberry thanks for checking in on this. The service team are working on a fix that they plan to deploy by the end of the month.
@seanbetts Awesome. Thank you for reporting back. I'll ask for this issue to be closed. Feel free to reopen is the planned solution and current communication with team becomes an issue. #please-close