Skip to main content
Version: 2.1.0

Premature Termination of Tasks

If the microservice is not busy, once a recording is uploaded, the processing begins. The processing time can vary anywhere between a few milliseconds to several minutes depending on technology, model, etc. Should the need arise to cancel a task mid-process, it is indeed feasible.

Cancellation Mechanism

Task cancellation occurs automatically when the client's connection is closed. However, it's important to note that the cancellation process is not instantaneous.

Delay in task termination

Terminating a task takes some time. Consequently, even after the client connection is closed, the microservice remains occupied with the cancellation process. Hence another task sent immediately after closing the connection may encounter a busy microservice. The duration required for terminating a running task depends on several factors, including the type of technology, processing stage, and hardware capabilities. Technologies like Speaker Diarization and Voiceprint Extraction usually terminate tasks in the order of milliseconds. Terminating a Speech to Text Whisper Enhanced task, on the other hand, may take up to 30 seconds in the worst-case scenario.