Current Behavior:
Calling upload.transcribe creates a transcription record, but does not trigger the server to start transcribing the file.
Expected Behavior:
Calling upload.transcribe should create a transcription record and trigger the server to begin transcribing the file.
Steps to Reproduce:
- Create a new upload.
- Delete any existing transcription related to that upload.
- Fetch the upload using the gem.
- Call the transcribe method on the upload.
You’ll notice that:
- The transcription gets created with a status of
awaiting.
- However, the transcription process never starts, and the status will not change to completed.
Additional Notes:
This issue occurs because the transcribe method only creates the transcription record without sending a signal to start the actual transcription process. Meeting have path for start transcription but upload doesn't yet.
/meeting/{meeting_id}/transcribe/{language}
/meeting/{meeting_id}/retranscribe/{language}
Current Behavior:
Calling
upload.transcribecreates a transcription record, but does not trigger the server to start transcribing the file.Expected Behavior:
Calling
upload.transcribeshould create a transcription record and trigger the server to begin transcribing the file.Steps to Reproduce:
You’ll notice that:
awaiting.Additional Notes:
This issue occurs because the transcribe method only creates the transcription record without sending a signal to start the actual transcription process. Meeting have path for start transcription but upload doesn't yet.
/meeting/{meeting_id}/transcribe/{language}/meeting/{meeting_id}/retranscribe/{language}