search

microsoft / BotFramework-Composer

Dialog creation and management for Microsoft Bot Framework Applications
https://docs.microsoft.com/en-us/composer/
MIT License
870 stars 371 forks source link

ChitChat and LUIS not working in a new Assistant Core template project (existing qna/luis resources) #6772

Closed darrenj closed 3 years ago

darrenj commented 3 years ago

Describe the bug

Creating a new Assistant Core template, choosing existing LUIS and QNA Azure resources and clicking start results in a conversational experience that doesn't seem to work. Both LU triggers (e.g. Help) and QnA/ChitChat ("hello") don't seem to be processed correctly.

Version

1.4.0-nightly.232669

Browser

OS

To Reproduce

Steps to reproduce the behavior:

  1. Create new Assistant Core template
  2. Using "rocket ship" UX, select existing QnA and LUIS resources already provisioned in Azure
  3. Start Bot
  4. Test in webchat - "help" and "hello"

No errors/warnings surfaced in Composer output/trace windows

Expected behavior

The assistant core functionality (LU and QNA) to work.

Screenshots

image

Additional context

darrenj commented 3 years ago

In the latest build (1.4.0-nightly.234518) LUIS does now appear to work however QnA is still causing an issue. I do now see in Composer trace this error : Unable to get a value for EndpointKey from state.

image

benbrown commented 3 years ago

@darrenj Should be resolved by #6881 please re-open if you still experience this!

darrenj commented 3 years ago

Now getting a qnamaker runtime error when starting the Bot (new project using the basic assistant template) on 1.4.0-nightly.236490. Selected existing QnA and LUIS keys in my Azure subscription.

image

Not seeing any other debug information - built Composer locally and spotted this (doesn't really help)

POST /api/projects/82249.18508397325/build 400 14189.853 ms - 51
darrenj commented 3 years ago

I've tested with the latest nightly have have the same qnamaker build error: 1.4.0-nightly.237504. I created a brand new basic assistant inside Composer, selected an existing LUIS and QnAMaker key and hit start...

darrenj commented 3 years ago

Resolved in latest nightly. There is another issue relating to QnAMaker resources that have exceeded azure index quotas which leads to an obscure runtime error inside Composer, opening another bug to track