408 Status code in Azure Speech to text Batch transcription

Question

I am trying to transcribe an audio file with Azure speech to text Batch transcription. The transcription is successful. But when I try to get the transcription files using the below API

curl -v -X GET "https://YourServiceRegion.api.cognitive.microsoft.com/speechtotext/v3.2/transcriptions/YourTranscriptionId/files" -H "Ocp-Apim-Subscription-Key: YourSubscriptionKey"

I am getting 408 status code.

Answer 1

Hello Bhaswati Saha,

Welcome to the Microsoft Q&A and thank you for posting your questions here.

I understand that you are having 408 Status code error, while performing Azure Speech to text Batch transcription.

The error is an "HTTP 408 Request Timeout" status code showing that the server did not receive a complete request from the client within the expected time. However, in the context of Azure Batch Transcription, this can also occur if the transcription results are not yet fully processed or available (even if the transcription job itself is marked as "Succeeded").

You can resolve the issue by these following step-by-step:

1. Ensure the transcription job status is succeeded by using the following bash command:

      curl -v -X GET "https://YourServiceRegion.api.cognitive.microsoft.com/speechtotext/v3.2/transcriptions/YourTranscriptionId" \
                -H "Ocp-Apim-Subscription-Key: YourSubscriptionKey"
   

2. If the status is succeeded, wait a few moments and retry the GET /files endpoint:

      curl -v -X GET "https://YourServiceRegion.api.cognitive.microsoft.com/speechtotext/v3.2/transcriptions/YourTranscriptionId/files" \
                -H "Ocp-Apim-Subscription-Key: YourSubscriptionKey"
   

3. Make sure the service region, transcription ID, and subscription key are correct and valid.
4. Increase the timeout duration in your request:

       curl --max-time 120 -X GET "https://YourServiceRegion.api.cognitive.microsoft.com/speechtotext/v3.2/transcriptions/YourTranscriptionId/files" \
                -H "Ocp-Apim-Subscription-Key: YourSubscriptionKey"
   

   You can also, implement retry logic to handle potential delays.
5. Also, check for a nextLink in the response and use it to fetch additional files if the transcription has many files.
6. If the issue persists, check the Azure Status Dashboard for any ongoing issues with the Speech to Text service. - https://status.azure.com/

I hope this is helpful! Do not hesitate to let me know if you have any other questions or clarifications.

---

Please don't forget to close up the thread here by upvoting and accept it as an answer if it is helpful.