Error starting transcription?

Starting the transcription seems hit or miss…It works about 60% o the time to start it. When it fails to start, I often see this:

VM21265:3 Error starting transcription: Switch to soup failed. Could not start transcription: timed out waiting for forced switch to sfu

Any advice?


  • Tamara
    Tamara Moderator, Dailynista admin

    Hi Zarally,

    We're sorry to hear that you're running into these issues while using the transcription API. This looks like the user who was attempting to call startTranscription() failed to receive an acknowledgement from the SFU, due to possible issues on their connection/network, which is why they received a timed out waiting for forced message.

    One possible workaround to bypass a specific user being unable to call startTranscription() due to connection issues is to start the transcription via the REST API: which should result in fewer timeout issues and failed transcriptions.

    If this is not a solution that works for you, would you be able to share any sessionIDs with us in which this error occurred? You can share with us here or at [email protected], and we'll help you debug from there.