Problem with order of events in MediaConvert API destination

Question

We have set a rule in EventBridge for MediaConvert to send statuses PROGRESSING, COMPLETE and ERROR to our API as destination. We store the statuses in the db identified by the date and time of receiving. The problem is that for some cases we receive the COMPLETE status first and then PROGRESSING after a few seconds. Is this normal to receive the statuses in this order?

Answer

It is not normal for the MediaConvert service to send the COMPLETE status before the PROGRESSING status. Generally, you should receive the events in the following order: PROGRESSING, (potentially multiple times), then COMPLETE or ERROR.

Network latency, temporary service disruptions, or other factors can sometimes cause events to be delayed or delivered out of order. While it's not common, it can happen. to detect such things you can monitor your AWS infrastructure and the MediaConvert service using Amazon CloudWatch to identify any potential issues that might be causing unusual event order or delays.

Problem with order of events in MediaConvert API destination

Relevant content