"Internal server error" from Azure on Filipino speech-to-text

Question

We have been using Azure speech-to-text / transcription services for generating transcripts. Recently (I first noticed this on Monday 9 December 2024) we have seen a very high chance of "Internal server error" in the transcription result of pil-PH language.

Please note that this is not about an API call returns 500 error. This about Azure reporting the transcription result as "Failed" and the failure reason as "Internal server error"

Below is a recent example:

{
            "self": "https://australiaeast.api.cognitive.microsoft.com/speechtotext/v3.2/transcriptions/9bab54ff-2a6b-46b0-802f-3e8d8d31eb1b",
            "model": {
                "self": "https://australiaeast.api.cognitive.microsoft.com/speechtotext/v3.2/models/base/13c027fa-5088-403f-85fb-c85b3c24c980"
            },
            "links": {
                "files": "https://australiaeast.api.cognitive.microsoft.com/speechtotext/v3.2/transcriptions/9bab54ff-2a6b-46b0-802f-3e8d8d31eb1b/files"
            },
            "properties": {
                "diarizationEnabled": true,
                "wordLevelTimestampsEnabled": true,
                "displayFormWordLevelTimestampsEnabled": true,
                "channels": [
                    0,
                    1
                ],
                "punctuationMode": "Automatic",
                "profanityFilterMode": "None",
                "timeToLive": "P1D",
                "error": {
                    "code": "Internal",
                    "message": "Internal server error."
                },
                "diarization": {
                    "speakers": {
                        "minCount": 1,
                        "maxCount": 35
                    }
                }
            },
            "lastActionDateTime": "2024-12-11T13:49:34Z",
            "status": "Failed",
            "createdDateTime": "2024-12-11T13:48:47Z",
            "locale": "fil-PH",
            "displayName": "1177d10a-b7c5-11ef-a940-02e06e3f16fc"
        },

Is this a known issue? Is there an ETA to have it fixed? Has anyone seen the same error too?

Thanks,

James

Answer 1

@James Hu Apologies for the late reply. I was discussing this internally with our product Owners.

It is caused by an issue on our side. We have identified the fix which is ready for deployment.

.

The fix should be deployed globally to all regions by end of this week. Hope this helps

**

Please do not forget to "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.