Unprocessable images
The Unprocessable Images report on the Image and Video Manager dashboard lists all of the pristine images 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 images are processed correctly.
Image processing fails for one of four reasons:
- The image is not processable for specific and known reasons
- The image exceeds system limits
- System limits are exceeded during processing
- The image is corrupt in some way
Pristine image is unprocessable for a specific and known reason
| Message | Details | Action |
|---|---|---|
| Pristine image not found | The pristine image to be processed could not be found. | Check your settings to make sure you are trying to process only actual image files. |
| Pristine image is in an unrecognized format | The pristine image is in an unrecognized or unsupported format. | Check your settings to make sure you are trying to process only supported image formats. See Best practices for pristine images for a list of supported and unsupported formats. |
| Pristine image request redirects and changes the URL scheme | The pristine image 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 image or a subrequest (for example, Composite) is malformed. | Make sure that any reserved or unsafe characters in the URI are properly encoded. |
| Invalid policy | The pristine image could not be processed because the policy being applied to it is invalid (for example, the policy name specified does not exist), or policy variables are being used and bad data is received. | Check that the policy specified exists and the policy name is correct. |
Pristine image exceeds system limits
| Message | Details | Action |
|---|---|---|
| Size of ___ exceeds the limit of ___ | The pristine image could not be processed because the size of the resulting file exceeds the limit. | For more information about image byte size, see Best practices for pristine images. |
| Pristine image is too wide | The pristine image could not be processed because it is too wide. | For more information about image dimensions, see Best practices for pristine images. |
| Pristine image is too tall | The pristine image could not be processed because it is too tall. | For more information about image dimensions, see Best practices for pristine images. |
| Pristine image has too many bytes | The pristine image could not be processed because it is too large. | For more information about image file size, see Best practices for pristine images. |
System limits are exceeded during processing
| Message | Details | Action |
|---|---|---|
| Image processing took too long | The image 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 image in the intermediary steps. |
Pristine image is corrupt
If you see this message, the pristine image 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 image may have been corrupted during your publishing process.
To identify the issue with the image, download and open the image using a tool that identifies its format and characteristics. There are many such tools freely available—for example, the open source tool imagemagick.
The tool you choose should allow you to print out or view any issues encountered while processing the image.
Updated over 2 years ago