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
{{ message }}
This repository has been archived by the owner on Oct 17, 2024. It is now read-only.
I’m deploying FAQ Plus and facing issue with the multi turn chat in Teams.
When I ask the bot a question, it responds with the multi turn options, however when I click on one of the options it responds with “I didn't find a matching answer for this question. Do you want me to ask an expert?". If I copy the exact question and enter it in chat it responds correctly. The bot is unable to respond when I select from the multi turn options but if I type the question, it responds correctly. The multi turn is working fine in the qnamaker. I’ve tried the same knowledge base with another webapp bot I created in Azure and it works correctly, so nothing is wrong in the knowledge base itself.
The text was updated successfully, but these errors were encountered:
Thank you for raising the query and sharing all the details, we've identified this as a bug, will triage it and let you know when it'll be addressed. But as a work around, users can still type the question to get the answer from the bot, request to use the work around for now.
I’m deploying FAQ Plus and facing issue with the multi turn chat in Teams.
When I ask the bot a question, it responds with the multi turn options, however when I click on one of the options it responds with “I didn't find a matching answer for this question. Do you want me to ask an expert?". If I copy the exact question and enter it in chat it responds correctly. The bot is unable to respond when I select from the multi turn options but if I type the question, it responds correctly. The multi turn is working fine in the qnamaker. I’ve tried the same knowledge base with another webapp bot I created in Azure and it works correctly, so nothing is wrong in the knowledge base itself.
The text was updated successfully, but these errors were encountered: