Forum Discussion

aka8941's avatar
aka8941
Copper Contributor
Sep 15, 2023

Error message - Generating transcript

"We're having trouble generating a transcript and captions right now. Try again in a bit." is the error message our video team sees when generating transcripts. They have to wait around ten minutes and refresh the page for it to clear, which is a major annoyance. What is this error, and why is it happening?

  • Elsa_ElenaV's avatar
    Elsa_ElenaV
    Copper Contributor

    Hello everyone,

    I recorded a meeting 7 days ago and have been trying to generate the transcript without success. I keep getting this error message:

    "You need a transcript first

    We're having trouble generating a transcript and captions right now. Try again in a bit."

    I've encountered this issue before, but usually, the transcript is generated when I try again the next day. Unfortunately, this time it hasn't worked. Any help would be appreciated.

    Thank you!

  • karen_dredske's avatar
    karen_dredske
    Steel Contributor
    Bet it is because of the change over happening on the platform with Stream Classic going away. . . but 10 min isn't really a big deal. I remember 2 years ago when it would take up to 3 hours. I know patience is hard to come by, but as long as it is completing - that is the important part.
    • aka8941's avatar
      aka8941
      Copper Contributor
      Thanks Karen. I didn't know it would take that long before. Appreciate the perspective.
      • Hao_Moy's avatar
        Hao_Moy
        Icon for Microsoft rankMicrosoft
        Hello! I'm Hao and I'm part of the transcription team on Stream. Sorry you've been experiencing issues with generating transcripts. That error message could be for a number of reasons. If you're able to reload and execute a transcription generation after a while it makes me think that traffic was high at that time, making new requests unstable. We have initiatives going on to increase the reliability and robustness of our transcription experience.
        Reloading and trying again a little later is the best avenue here - feel free to reach out if this problem persists.

Resources