Skip to content

[BUG]The "follow-up tasks" in Azure AI Language Summarization is not working #44908

@JohanKlijn

Description

@JohanKlijn

Library name and version

Azure.AI.Language.Conversations 1.1.0

Describe the bug

When using the Azure AI Language Service to create a "recap and follow-up task summarization" accoording to this example: https://learn.microsoft.com/en-us/azure/ai-services/language-service/summarization/how-to/conversation-summarization#get-recap-and-follow-up-task-summarization I get the follwoing exception:

{
   "error": {
       "code": "InvalidRequest",
       "details": [
           {
               "code": "InvalidRequest",
               "message": "Job task: 'ConversationalSummarizationTask-summary_narrative' failed with validation error: Invalid value for parameter 'summaryAspects', valid values are issue, resolution, chapterTitle, narrative, recap."
           }
       ],
       "message": "Invalid Request.",
       "innererror": {
           "code": "InvalidParameterValue",
           "message": "Job task: 'ConversationalSummarizationTask-summary_narrative' failed with validation errors: ['Invalid parameter in request']"
       }
   }
}

So specifying a task with a summaryAspects of "follow-up tasks" doesn't work.

Example:

{
    "taskName": "Conversation Task 1",
    "kind": "ConversationalSummarizationTask",
    "parameters": {
        "summaryAspects": [
            "recap",
            "follow-up tasks"
        ]
    }
}

Expected behavior

follow-up tasks are created

Actual behavior

exception.

Reproduction Steps

Just use the example

Environment

.NET 8.0

Metadata

Metadata

Assignees

No one assigned

    Labels

    ClientThis issue is related to a non-management packageCognitive - LanguageService AttentionWorkflow: This issue is responsible by Azure service team.customer-reportedIssues that are reported by GitHub users external to the Azure organization.needs-team-attentionWorkflow: This issue needs attention from Azure service team or SDK teamquestionThe issue doesn't require a change to the product in order to be resolved. Most issues start as that

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions