Important: Bug reports submitted here should relate specifically to the open source sample amazon-transcribe-live-meeting-assistant project. Do not submit bugs related directly to any AWS service.
If your issue relates to Amazon Transcribe, Amazon Bedrock or Amazon Bedrock Knowledge Base - setup, user provisioning, document ingestion, accuracy, or other aspects of the service, then first check the service documentation, and then reproduce the problem using the relevant AWS service console before engaging AWS support directly. Thank you.
Describe the bug
We had an odd issue with the last meeting we tried to record with LMA. The meeting ran 1.5 hours but LMA shows the duration as 39 minutes and 39 seconds and appears to have only transcribed and summarized the first 39 minutes and 39 seconds of the meeting. Oddly, it still shows a full length (1.5 hours) audio recording of the meeting and the bot never gave any indication of an issue even though I was using the Chrome browser extension to record. Checking some of the logs, I noticed the TranscriberWebsocket logs had an error at the same time the transcribing stopped
BadRequestException: The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.
And the next log after that was when the meeting ended nearly an hour later.
To Reproduce
Unknown trigger, seems to be random
Expected behavior
Bot is able to recover from error and continue transcribing, or notifies users that recording has failed and needs to be restarted.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
More details provided offline to Bob and Xuejie
Important: Bug reports submitted here should relate specifically to the open source sample amazon-transcribe-live-meeting-assistant project. Do not submit bugs related directly to any AWS service.
If your issue relates to Amazon Transcribe, Amazon Bedrock or Amazon Bedrock Knowledge Base - setup, user provisioning, document ingestion, accuracy, or other aspects of the service, then first check the service documentation, and then reproduce the problem using the relevant AWS service console before engaging AWS support directly. Thank you.
Describe the bug We had an odd issue with the last meeting we tried to record with LMA. The meeting ran 1.5 hours but LMA shows the duration as 39 minutes and 39 seconds and appears to have only transcribed and summarized the first 39 minutes and 39 seconds of the meeting. Oddly, it still shows a full length (1.5 hours) audio recording of the meeting and the bot never gave any indication of an issue even though I was using the Chrome browser extension to record. Checking some of the logs, I noticed the TranscriberWebsocket logs had an error at the same time the transcribing stopped
BadRequestException: The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.And the next log after that was when the meeting ended nearly an hour later.To Reproduce Unknown trigger, seems to be random
Expected behavior Bot is able to recover from error and continue transcribing, or notifies users that recording has failed and needs to be restarted.
Screenshots If applicable, add screenshots to help explain your problem.
Additional context More details provided offline to Bob and Xuejie