Skip to content
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

Connect to QnA knowledgebase not working #1517

Closed
2 of 7 tasks
jelleDK opened this issue Nov 6, 2019 · 2 comments
Closed
2 of 7 tasks

Connect to QnA knowledgebase not working #1517

jelleDK opened this issue Nov 6, 2019 · 2 comments
Labels
Bot Services Required for internal Azure reporting. Do not delete. Do not change color. customer-replied-to Required for internal reporting. Do not delete. customer-reported Required for internal Azure reporting. Do not delete.

Comments

@jelleDK
Copy link

jelleDK commented Nov 6, 2019

When i try to use the Connect to QnA Knowledgebase and fill all the details in the Settings i get the following error in my emulator: Unable to find a QnA Maker service with Knowledge Base ID xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx. Please add a QnA Maker service to your bot. I tested my knowledgebase through postman and there it works so either I'm doing something wrong in composer or there's a bug.

Version: Application SHA 9e3347c4

Browser

What browser are you using?

  • Chrome
  • Safari
  • Firefox
  • Edge

OS

What operating system are you using?

  • macOS
  • Windows
  • Ubuntu

To Reproduce

Steps to reproduce the behavior:
I just added the option in my dialog and filled in the settings

Screenshots

image
image

@jelleDK jelleDK added the Needs-triage A new issue that require triage label Nov 6, 2019
@cwhitten cwhitten added Bot Services Required for internal Azure reporting. Do not delete. Do not change color. customer-reported Required for internal Azure reporting. Do not delete. and removed Needs-triage A new issue that require triage labels Nov 6, 2019
@cwhitten
Copy link
Member

cwhitten commented Nov 6, 2019

hello @jelleDK and thank you for raising the issue. A known issue is causing this:

#483

Restarting Composer by killing the running processes and invoking another yarn startall should fix this. Can you try and report back?

Addressing this issue is being tracked here: #1516

@cwhitten cwhitten added the customer-replied-to Required for internal reporting. Do not delete. label Nov 6, 2019
@jelleDK
Copy link
Author

jelleDK commented Nov 7, 2019

hello @jelleDK and thank you for raising the issue. A known issue is causing this:

#483

Restarting Composer by killing the running processes and invoking another yarn startall should fix this. Can you try and report back?

Addressing this issue is being tracked here: #1516

This did the job for me thanks!

@jelleDK jelleDK closed this as completed Nov 7, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bot Services Required for internal Azure reporting. Do not delete. Do not change color. customer-replied-to Required for internal reporting. Do not delete. customer-reported Required for internal Azure reporting. Do not delete.
Projects
None yet
Development

No branches or pull requests

2 participants