1 Answer
- Newest
- Most votes
- Most comments
0
Hi,
Thanks for reaching out and apologies for the delayed response. I would just like to confirm that we have reached out to the Transcribe service team regarding this behavior.
The service team investigated the issue and has confirmed that this is indeed a bug. They have a fix for this bug that is currently pending deployment.
We will let you know once we have received further updates. Thanks in advance for your patience!
Relevant content
- asked a year ago
- asked a year ago
- asked 2 years ago
- AWS OFFICIALUpdated 8 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 4 months ago
- AWS OFFICIALUpdated a year ago
This is great! Thank you for the update!!
Hi, there! Checking in to see if the aforementioned bug fix has been pushed to prod... Thank you!