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
Need to add retry chapter feature to transcribe failed chapter.
Need a solution to track the in progress status and show in the UI in case of retry or failed chapter.
Need a solution when to stop conversion process in case of error happened and stored in tts_msg in UI side.
Transcription current issue in UI:
Currently, From the backend, it's only checking through stt_msg field from Verse table. In case of error, Verse table will hold the stt error message in stt_msg column. In the frontend logic, It's checking if stt_msg !== "Transcription successful", it's assuming chapter to have error. So, in case of book retry, it will set to error status in the frontend side since, it's dependent on stt_msg from the db.
Similarly, in case of chapter retry, it will still set to error status.
Possible fix could be to clear out the stt_msg in the db if it's other than "Transcription successful" before making AI api call.
The text was updated successfully, but these errors were encountered:
Transcription current issue in UI:
Currently, From the backend, it's only checking through stt_msg field from Verse table. In case of error, Verse table will hold the stt error message in stt_msg column. In the frontend logic, It's checking if stt_msg !== "Transcription successful", it's assuming chapter to have error. So, in case of book retry, it will set to error status in the frontend side since, it's dependent on stt_msg from the db.
Similarly, in case of chapter retry, it will still set to error status.
Possible fix could be to clear out the stt_msg in the db if it's other than "Transcription successful" before making AI api call.
The text was updated successfully, but these errors were encountered: