Potential Error Causing Rerun of Old Transcoding Jobs on April 11th

Question

Hi,

On April 11th, our AWS account experienced an unexpected behaviour where old Transcoding jobs seemed to have been rerun.

We are thoroughly reviewing our system logs and configurations, to check for the reason of the issue and also wonder if this might have been an issue on the AWS side or a potential bug within AWS MediaConvert we use for transcoding.

Did AWS experience any known disruptions, service outages, or incidents related to transcoding or related services on April 11th?
Were there any updates, changes, or releases made to AWS services that could have potentially affected the transcoding functionality on or around that date?

Best regards

Answer

Riva, thank you for your question.
Please submit this to AWS Support for proper processing and analysis of the issue.

Also, if your transcoding workflow uses automation to create MediaConvert jobs (ex. S3 bucket -> Lambda -> MediaConvert job) you may want to validate that source file dates were not change or updated for some reason. (Or Versioning was enabled in S3 bucket.) Depending on how the automation triggers are configured, source files with new dates may be seen as new and kick off transcoding.

Potential Error Causing Rerun of Old Transcoding Jobs on April 11th

Conteúdo relevante