Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Speech2Text API does not accept an Object in customeProperties field anymore #32450

Open
mthnyldrm opened this issue Feb 4, 2025 · 0 comments
Labels
Cognitive - Speech customer-reported Issues that are reported by GitHub users external to the Azure organization. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Attention Workflow: This issue is responsible by Azure service team.

Comments

@mthnyldrm
Copy link

Requests to transcribe failed with BadRequest from 15.01.2025.
Microsoft updated API in silent mode

The problem is - when we are sending request to transcribe in payload we send this field

"customProperties": {
"retryCount": 0,
"DevEnvName": "local",
"Provider":"Cloud9Client"
}

customeProperties was key value pair <string, object> they changed to <string, string>
and now we have BadRequest with the next error
{
"code": "InvalidPayload",
"message": "$.customProperties.retryCount: The supplied value is invalid."
}

@microsoft-github-policy-service microsoft-github-policy-service bot added question The issue doesn't require a change to the product in order to be resolved. Most issues start as that customer-reported Issues that are reported by GitHub users external to the Azure organization. labels Feb 4, 2025
@v-jiaodi v-jiaodi added Service Attention Workflow: This issue is responsible by Azure service team. Cognitive - Speech labels Feb 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Cognitive - Speech customer-reported Issues that are reported by GitHub users external to the Azure organization. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Attention Workflow: This issue is responsible by Azure service team.
Projects
None yet
Development

No branches or pull requests

2 participants