Conflicts of Generative Answers and Fallback Topic (in Managed Solution)

(0) Share

Report

Posted on by ryjan

Hi,

is there any way how to prioritize the Conversational boosting and Fallback topics?

Once the Fallback Topic is active, the Conversational boosting topic is not triggered, so no answers are produced.

I have resolved this by switching off the Fallback and Multiple Results topics.

BUT - after deployment to another environment within a managed solution, the Fallback and Multiple Results topics are active, cannot be deactivated, and the Conversational boosting topic is not triggered.

Any best practice?

Categories:

Topic creation & management

I have the same question (0)

All responses (5)

Answers (1)

Verified answer

HenryJammes on at

Like (0)

Report

Hi @ryjan

By default, the Conversational Boosting topic will trigger before Fallback on the unknown intent event.
If you switch to the code editor view of the Conversational Boosting system topic, you can see it actually has a priority of -1.
If no generative answer is found, then it goes to Fallback.
That's the standard logic, you can tweak the experience so that generative answers triggers when you decide in your bot logic.

Henry

Was this reply helpful? Yes No
ryjan 45 on at

Like (0)

Report

Hi @HenryJammes, thanks for your reply. Now I am facing the issue that Conversational Boosting topic is triggered, but it does not produce any result in managed environment. Source files are stored in Upload a document (preview) section. They are transferred with the solution to managed environment, but there is no AI response
See screenshot of the managed solution
Find activities from Conversation Transctipt table.
Unmanaged:

"valueType":"GPTAnswer",
"id":"a61dfc81badf4dc6afd02ba30153d145",
"type":"trace",
"timestamp":1709045738,
"from":{
"id":"426823bc-046e-16eb-d98f-5a57e72ed94a",
"role":0
},
"replyToId":"c1-594899c5-8285-4a88-ad82-1aff8d996916",
"value":{
"gptAnswerState":"Answered"
}

Managed:

{
"valueType":"GPTAnswer",
"id":"5f77358cf59540688beb1f4701ae244e",
"type":"trace",
"timestamp":1709045837,
"from":{
"id":"01e6e859-97ff-0bc0-70a0-0d4171b57657",
"role":0
},
"replyToId":"c1-5a39f9fe-7774-41e6-ab1e-294b169cdb54",
"value":{
"gptAnswerState":"No Search Results"

Was this reply helpful? Yes No
HenryJammes on at

Like (0)

Report

Is Dataverse Search enabled in that environment? Maybe the files haven't been indexed yet.
@mboninco

Was this reply helpful? Yes No
mboninco on at

Like (0)

Report

The most likely cause is that the files are not indexed. We probably need a mechanism to re-trigger the indexing of the files in this situation.

Was this reply helpful? Yes No
ryjan 45 on at

Like (0)

Report

@HenryJammes Dataverse search was not enabled indeed. It is enabled now. I have triggered another deployment with Dataverse search already enabled. But the issue prevails.
@mboninco any way how to re-trigger the indexing manually?

Was this reply helpful? Yes No