Answered

Fallback Topic is triggering after Conversational Boosting generates an answer.

(0) Share

Report

Posted on by JaseOfSpades

Since the UI was modernised recently, my fallback topic has started triggering even when the Conversational Boosting Topic creates an answer using the Create generative answers step.

I can't say for sure if this is related to the recent changes, but I can't seem to figure out a way to stop it fallback Topic from triggering when the answer is created.
My guess is that it has something to do with the fact that both Topics are via 'On Unknown Intent' but changing the priority doesn't do anything. So I assume that I will need to set the Answer variable to something, though this was automatic beforehand.

Categories:

Topic creation & management

I have the same question (0)

All responses (3)

Answers (1)

Umianta 290 on at

Like (1)

Report

Hi @JaseOfSpades

recently attempted similar steps with generative answers and did not encounter this issue.
Please try creating a new Chatbot and check again. Additionally, you can end the execution by adding an End Topic/End Conversation node.

If this was helpful:
⭐Please mark it as a solution
⭐Give me a thumbs-up
⭐Connect on LinkedIn
⭐I consistently upload technical videos. If you're interested, please visit and subscribe to my YouTube Channel
⭐Always glad to help, Umesh Khandelwal!

Was this reply helpful? Yes No
Verified answer

JaseOfSpades on at

Like (1)

Report

Thanks, @Umianta

Creating a new copilot did indeed remove the issue of it answering it but still saying it couldn't answer the question. However, for those that have put more time into their copilots than I initially had and didn't want to recreate them, here was another solution that me and a colleague put together to remove the issue without recreating your already established copilot:

It would seem that the main issue was that it was going to the Fallback topic even if the conversational boosting topic found an answer. The System.FallbackCount returned as 0 when we got an answer generated but if it was unable to find an answer it would be 1 or more depending on how many attempts it tried to find an answer via the user rephrasing their prompt.

So to resolve this (as seen in the topic screenshot above), we added nested conditions to handle the instances that it would have the answer (System.FallbackCount = 0) and when it couldn't find an answer (System.FallbackCount not 0). The additional checks based on FallbackCount are simply to allow for an alternative text being returned after so many attempts.

Was this reply helpful? Yes No
CU16081349-0 on at

Like (0)

Report

Hi @Umianta I’m stuck with the same problem right now can you please let me know the steps which you followed to resolve this issue some repro steps would help me as I’m new to copilot studio

Was this reply helpful? Yes No