The Unprocessable Videos report on the Image and Video Manager dashboard lists all of the pristine videos that could not be processed in the past 24 hours, along with the reason processing failed. The possible messages are listed below along with the actions you can take to make sure that all videos are processed correctly.

Video processing fails for one of four reasons:

The video is not processable for specific and known reasons
The video exceeds system limits
System limits are exceeded during processing
The video is corrupt in some way

Pristine video is unprocessable for a specific and known reason

Message	Details	Action
Unparseable video: failed to identify pristine video	The input file could not be processed because it could not be identified as a video. It could be missing a valid file extension, or it may have a valid file extension but not actually be video file.	Check your settings to make sure you are trying to process only actual video files.
Pristine video not found	The pristine video to be processed could not be found.	Check your settings to make sure you are trying to process only actual video files.
Pristine video is in an unrecognized format	The pristine video is in an unrecognized or unsupported format.	Check your settings to make sure you are trying to process only supported video formats. See Best practices for pristine videos for a list of supported and unsupported formats.
Pristine video request redirects and changes the URL scheme	The pristine video requests a redirect from HTTPS to HTTP or vice versa. This is not permitted.	Check your property configuration for this type of redirect and make any necessary changes.
Invalid URI	The URI for the pristine video is malformed.	Make sure that any reserved or unsafe characters in the URI are properly encoded.
Invalid policy	The pristine video could not be processed because the policy being applied to it is invalid (for example, the policy name specified does not exist).	Check that the policy specified exists and the policy name is correct.

Pristine video exceeds system limits

Message	Details	Action
Size of ___ exceeds the limit of ___	The pristine video could not be processed because the size of the resulting file exceeds the limit.	For more information about video byte size, see Best practices for pristine videos.
Pixel total of ___ exceeds limit of ___ pixels	The pristine video could not be processed because the total number of pixels in the resulting video exceeds the limit.	For more information about video dimensions, see Best practices for pristine videos.
Duration of ___ exceeds limit of ___	The video was not processed because processing took too long.	Make sure the video conforms to the recommendations in Best practices for pristine videos.
Sample Rate of ___Hz exceeds limit of 60.00 Hz	The video was not processed because processing took too long.	Make sure the video conforms to the recommendations in Best practices for pristine videos.
Pristine video is too wide	The pristine video could not be processed because it is too wide.	For more information about video dimensions, see Best practices for pristine videos.
Pristine video is too tall	The pristine video could not be processed because it is too tall.	For more information about video dimensions, see Best practices for pristine videos.
Pristine video has too many bytes	The pristine video could not be processed because it is too large.	For more information about video file size, see Best practices for pristine videos.

System limits are exceeded during processing

Message	Details	Action
Video processing took too long	The video could not be processed because processing took too long.	Make sure your policy doesn't contain an overly complex sequence of artistic transformations that are causing the process to time out—for example, both enlarging and shrinking the video in the intermediary steps.

Pristine video is corrupt

If you see this message, it means that the pristine video at your origin is corrupt in some way.

It could be that the file itself is corrupt due to an error that occurred when the file was created, or the video may have been corrupted during your publishing process.

To identify the issue with the video, download and open the video using a tool that identifies its format and characteristics. The tool you choose should allow you to print out or view any errors encountered while processing the video.