-
Notifications
You must be signed in to change notification settings - Fork 377
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
Utterance is not passed to skill if disambiguation kicks in at parent #6431
Comments
Added tags, I'm assuming that the dialog provided when adding the |
@cleemullins @ryanlengel why was this transferred to the Composer project? Seems like it should to go the SDK |
@cwhitten (I asked.) The issue is in the specific choose intent trigger flow in Composer. It loses the turn.activity.text, hence I needed to modify the intent to cache it & use it later. I think the solution is to fix the choose intent flow in Composer. |
@cwhitten, this is feedback for the predefined dialog that Composer adds in the dialogFactory.ts. I'm not sure what area to label this under, assigning to you for triage. |
Filed for tracking (along with conversation)
Before I file it, I want to make sure I got it right.
Scenario:
• Root bot with Orchestrator
• Child bot with LUIS
• Routing works correctly.
• Without disambiguation child get’s utterance (turn.text?) and is able to trigger on it.
• Issue: With disambiguation: I suspect that utterance is not passed to skill, so skill cannot trigger on recognition.
Failure case (with disambiguation):
Repeated without disambiguation:
The text was updated successfully, but these errors were encountered: