Hi! It looks like when it is creating the custom vocabulary it's passing on to Transcribe incorrectly formatted words. I checked out the lambda function in charge of creating the vocabulary and in the example feed it is taking in the following terms
["-Hawn", "Cloud", "A-W-S-A-I-Services", "Amazon", "Code-Whisperer", "Pillir", "A-W-S", "S-A-P", "U-K-T-V", "Media-two-Cloud", "Marketplace", "Mainframe-Modernization", "E-M-R-Serverless", "E-M-R", "Apache", "Spark", "Hive", "Hawn", "Amazon-Connect", "Local-Measure", "low", "Intelligent-Automation"]
It seems that when creating a custom vocabulary "-word" (in this case -Hawn, is creating the issue) is not accepted, so the lambda function in charge of doing the preprocessing should be reviewed --> podcast-transcribe-index-createTranscribeVocabular***
Hope this helps!
When you create the custom vocabulary for Transcribe you have to check the characters that you can use for different languages. Here you can fine more details : https://docs.aws.amazon.com/transcribe/latest/dg/charsets.html.
For the specific language that you are using, you can check how you can deal with special characters.
Can't get AWS CLI transcribe outputkey formatted correctlyasked a month ago
Dynamic version of Amazon Transcribe Post Call Analyticsasked a month ago
Working of AWS transcribeasked a month ago
How do I use a custom vocabulary when using Amazon Transcribe streaming?asked a year ago
Amazon Transcribe Custom Vocabulary ERROR: invalid characters or incorrectly formatted termsAccepted Answerasked 2 months ago
Amazon Transcribe table format specifying IPAAccepted Answerasked 5 months ago
How to get the full list of words that Amazon Transcribe can recognize for a specific language?asked 5 months ago
Creating new custom vocabularies from a table is brokenasked 2 years ago
Amazon Transcribe > Custom Vocabularyasked a month ago
Amazon Transcribe Creating a custom vocabulary fail at line 2asked 6 months ago