- Newest
- Most votes
- Most comments
When a MediaConvert job has at least one output that encounters an error, MediaConvert sends an event with the status "ERROR". Based on the available information:
- The ERROR event does not appear to contain outputGroupDetails or outputDetails in its standard structure. The example ERROR event JSON shows a basic structure that includes:
- General event metadata (version, id, detail-type, source, account, time, region)
- Resources array containing the job ARN
- A detail object with timestamp, accountId, queue, jobId, status, errorCode, errorMessage, and userMetadata
There is no indication that the ERROR event includes information about successful outputs or file paths for outputs that completed successfully. The event focuses on communicating the error state rather than providing a comprehensive report of partial successes.
- The event does not appear to contain output-level status information. The ERROR status is applied at the job level, indicating that at least one output has an error, but the standard event structure doesn't break down the status by individual output.
When a MediaConvert job fails with an ERROR status, no outputs are written to your Amazon S3 bucket, even if some parts of the job were processed successfully before the error occurred. This is consistent with the all-or-nothing approach to job completion.
If you need detailed information about which specific outputs failed and which succeeded (if any), you would likely need to use the MediaConvert API to query additional job details beyond what's provided in the standard ERROR event.
Sources
Events with ERROR status - MediaConvert
List of MediaConvert EventBridge events - MediaConvert
Monitoring MediaConvert job progress - MediaConvert
Error codes - MediaConvert
If error code and provided information for particular job failure is not good enough for troubleshooting you need to open support ticket.
answered a year ago
Relevant content
asked 5 years ago
asked 2 years ago
