You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
A clear and concise description of what the bug is.
When using the Conditional Chaining demo with Elicit Response, when the bot prompts for First Name or Last name, the answer is not accepted, but instead the bot prompts with 'What is the question?".
To Reproduce
Steps to reproduce the behavior.
Load conditional chaining demo. OR by following the steps in the implementation guide on a bare-bones deployment.
When responding with a name, it replies with "What is the question?".
Expected behavior
A clear and concise description of what you expected to happen.
The bot should accept the provided input without prompting for 'Qhat is the question?"
Please complete the following information about the solution:
v5.2.1
Screenshots
If applicable, add screenshots to help explain your problem (please DO NOT include sensitive information).
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
Describe the bug
A clear and concise description of what the bug is.
When using the Conditional Chaining demo with Elicit Response, when the bot prompts for First Name or Last name, the answer is not accepted, but instead the bot prompts with 'What is the question?".
To Reproduce
Steps to reproduce the behavior.
Load conditional chaining demo. OR by following the steps in the implementation guide on a bare-bones deployment.
When responding with a name, it replies with "What is the question?".
Expected behavior
A clear and concise description of what you expected to happen.
The bot should accept the provided input without prompting for 'Qhat is the question?"
Please complete the following information about the solution:
Screenshots
If applicable, add screenshots to help explain your problem (please DO NOT include sensitive information).
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: