[BUG] Not receving knowledge base answers from Custom Question Answering with an Orchestration Workflow using SDK

Library name and version

Azure.AI.Language.Conversations 1.0.0-beta.3

Describe the bug

When using the ConversationAnalysisClient to retrieve predictions from an Orchestrator connected to a Custom Question Answering (CQA), and giving a valid question message, the result successfully predicts the CQA intent, however the answers collection is empty when it should contain the expected answer of the question.

Expected behavior

As it is documented in GitHub here, if the given question is valid, the Orchestration should return the answer for the question within the prediction result.

Actual behavior

When using the ConversationAnalysisClient and giving a valid question, the prediction is correct but the answers collection is empty.

Reproduction Steps

var endpoint = new Uri(@"https://<language_studio_name>.cognitiveservices.azure.com");
var credential = new AzureKeyCredential("<primary_key>");
var conversationAnalysisClient = new ConversationAnalysisClient(endpoint, credential);

var input = new TextConversationItem(participantId: "1", id: "1", text: message)
{
    Language = "es"
};

var opt = new AnalyzeConversationOptions(input);

Response<AnalyzeConversationTaskResult> response = 
    await _conversationAnalysisClient.AnalyzeConversationAsync(message, _conversationsProject, opt);

var customConversationalTaskResult = response.Value as CustomConversationalTaskResult;
var orchestratorPrediction = customConversationalTaskResult.Results.Prediction as OrchestratorPrediction;
var targetIntentResult = orchestratorPrediction.Intents[orchestratorPrediction.TopIntent];
var questionAnsweringTargetIntentResult = targetIntentResult as QuestionAnsweringTargetIntentResult;

KnowledgeBaseAnswers knowledgeBaseAnswers = questionAnsweringTargetIntentResult.Result;
var answers = knowledgeBaseAnswers.Answers; // THIS IS EMPTY, HOWEVER THERE SHOULD BE ANSWERS!!!

Environment

Windows 10 .NET 6.0 Visual Studio 2022 17.1.5

[rliberoff]

Hi @ChongTang!

The issue is fixed. Everything seems to be working as expected. This bug can be closed.

Thank you all for the great support and your help.

[ChongTang]

@rliberoff, the issue should be fixed. Can you try again?