You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are several issues with the error messages for YouTube transcripts that the backend returns to the frontend.
We have seen that the Python library we are using to fetch transcripts can report a TranscriptDisabled error in cases where this error code is misleading. For example we've seen it for long videos for which a transcript has not yet been generated, and videos with no sound.
The backend reports an HTTP 500 status, which parts of our monitoring will interpret as a backend failure, even though this is a "normal" failure.
The "details" message is the one from the underlying library, which tells users to file bug reports on the library's GitHub project. We don't want to send our users there. Instead the reports should go to us initially.
There are several issues with the error messages for YouTube transcripts that the backend returns to the frontend.
TranscriptDisabled
error in cases where this error code is misleading. For example we've seen it for long videos for which a transcript has not yet been generated, and videos with no sound.From a discussion on Slack we agreed to:
So far the errors we've seen have all had a
TranscriptDisabled
code, but see https://github.com/jdepoix/youtube-transcript-api/blob/master/youtube_transcript_api/_errors.py for other error codes we may encounter.The text was updated successfully, but these errors were encountered: