-
Notifications
You must be signed in to change notification settings - Fork 378
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
QnA Maker integration docs not working #2941
Comments
@fathorMB could you share more detail for the dialog file ? in the dialog flow, do you only include the QnA step or there are other steps may introduce this error ? |
@hibrenda the QnA step is the only one in the dialog. I also tried to put it in a separate dialog and directly in the intent recognized trigger, but fails the same way. I tried to put other steps to check if the problem was in my dialog but all other steps are working. |
if possible, could you share your bot (dialog) to us (no need to share qna) , we may have a try . |
@hibrenda It's pretty simple to reproduce. I just created a new bot from scratch and then added a intent recognized trigger with some of the questions i have in my QnA. I see that LUIS is recognizing correctly, the trigger is fired and it contains only the QnA block. Configured as you see in the screenshot, so as explained in the documentation. At runtime, when reaching the QnA block, the only bot response is the error i did include in the issue description. |
@fathorMB Thanks for reporting this issue. now I see . We test with qna sample and not reproduce this issue as all have been settled in the sample. |
@hibrenda I'll try and let you know. Thanks in advance for support |
@hibrenda It is now working filling all the fields you pointed out. Thank you! |
By the way in master branch, we do have improvement even if you leave these as empty. |
Describe the bug
We are trying to implement QnA Maker integration following the docs here: DOCS
We get the following error when the Connect to QnA Knowledgebase block is reached:
We already tried some different configurations, guided by other issues we found here flagged as closed.
Version
Application SHA
test
Branch: stable
Browser
OS
Expected behavior
We are exactly replicating the docs, so we expect it to work.
Screenshots
Additional context
Bypassing the appsettings way, we also tried "hardcoding" the configuration in the Connect to QnA Knowledgebase block but nothing changed.
Our bot is working properly with common LUIS operations, we used an Intent to route to QnA as suggested by docs.
We also tried to call QnA starting the Bot from VS. We obtain the same exception and it seems to be related to something happened here: Microsoft BotBuilder
@onoflo
@andreatosato
The text was updated successfully, but these errors were encountered: