Skip to content

Commit 141be4f

Browse files
committed
Explaining about Get Transcription status and running time
1 parent 977da5b commit 141be4f

1 file changed

Lines changed: 6 additions & 0 deletions

File tree

articles/ai-services/speech-service/batch-transcription-get.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -23,6 +23,9 @@ To get transcription results, first check the [status](#get-transcription-status
2323

2424
To get the status of the transcription job, call the [Transcriptions_Get](https://eastus.dev.cognitive.microsoft.com/docs/services/speech-to-text-api-v3-1/operations/Transcriptions_Get) operation of the [Speech to text REST API](rest-speech-to-text.md).
2525

26+
[!IMPORTANT]
27+
> Batch transcription jobs are scheduled on a best-effort basis. At pick hours it may take up to 30 minutes or longer for a transcription job to start processing. Most of the time during the execution the transcription status will be `Running`. This is because the job is assigned `Running` status the moment it moves to the batch transcription backend system, which happens almost immediately when base model is used, and slightly slower for custom models. Thus the amount of time a transcription job spends in `Running` state doesn't correspond to the actual transcription time, but also includes waiting time in the internal queues.
28+
2629
Make an HTTP GET request using the URI as shown in the following example. Replace `YourTranscriptionId` with your transcription ID, replace `YourSubscriptionKey` with your Speech resource key, and replace `YourServiceRegion` with your Speech resource region.
2730

2831
```azurecli-interactive
@@ -74,6 +77,9 @@ The `status` property indicates the current status of the transcriptions. The tr
7477

7578
::: zone pivot="speech-cli"
7679

80+
[!IMPORTANT]
81+
> Batch transcription jobs are scheduled on a best-effort basis. At pick hours it may take up to 30 minutes or longer for a transcription job to start processing. Most of the time during the execution the transcription status will be `Running`. This is because the job is assigned `Running` status the moment it moves to the batch transcription backend system, which happens almost immediately when base model is used, and slightly slower for custom models. Thus the amount of time a transcription job spends in `Running` state doesn't correspond to the actual transcription time, but also includes waiting time in the internal queues.
82+
7783
To get the status of the transcription job, use the `spx batch transcription status` command. Construct the request parameters according to the following instructions:
7884

7985
- Set the `transcription` parameter to the ID of the transcription that you want to get.

0 commit comments

Comments
 (0)