Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Retry chapter and status UI change implementation #84

Open
3 tasks
KetanKBaboo opened this issue Jan 7, 2025 · 0 comments
Open
3 tasks

Retry chapter and status UI change implementation #84

KetanKBaboo opened this issue Jan 7, 2025 · 0 comments
Assignees
Labels

Comments

@KetanKBaboo
Copy link

  • 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.

@KetanKBaboo KetanKBaboo added the UI label Jan 7, 2025
@KetanKBaboo KetanKBaboo self-assigned this Jan 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant