Documentation

Certain images are not showing thumbnail renditions in Adobe Experience Manager (AEM) as a Cloud Service - Asset

Last update: Mon May 05 2025 00:00:00 GMT+0000 (Coordinated Universal Time)

Specific images ingested into Adobe Experience Manager (AEM) as a Cloud Service - Assets fail to generate thumbnail renditions. This problem is linked to assets processed using the S3 bulk import tool, where the root cause involves unsupported file formats or corrupt source files. In some cases, digital rights management (DRM) approval pages are mistakenly downloaded as images due to data misalignment during migration. Verify asset integrity, inspect logs, confirm file format compatibility, and reprocess assets to ensure proper functionality within your AEM environment.

Description description

Environment

  • Adobe Experience Manager (AEM) as a Cloud Service - Assets
  • Ingestion using S3 bulk import tool

Issue/Symptoms

Certain images fail to display thumbnail renditions after being ingested into AEM. Symptoms include:

  • Rendition creation errors marked as Process failed.
  • Error messages indicating unsupported file formats or corrupt source files.
  • Thumbnail generation failure for assets with specific characteristics, such as small file sizes.
  • In some instances, files processed were not actual images but unintended document types, leading to rendition failures.

Resolution resolution

To resolve issues with missing thumbnail renditions, follow these steps:

  1. Check if the affected assets are corrupted or in unsupported formats. Review asset metadata for error messages such as:

    • Source asset seems to be corrupt (Input file contains unsupported image format).
    • UnsupportedFiles error indicating that the file format is not supported.
    • Ensure that files are genuine images and not unintended DRM approval pages.

  2. Access logs associated with rendition processing to identify specific errors. Look for entries related to the affected assets that provide details about failures during rendition creation.

  3. Identify which asset is experiencing a processing error and gather more details about the failure. As guidance, search the logs for entries similar to:

    [ **-asset-processing-*-assets-monitor-job]  com.adobe.cq.assetcompute.impl.scanprocess.AssetMonitorMBeanImpl Assets monitor found stuck processing asset: asset=/content/dam/< name> .jpg, state=processing, processingID=< id>

    • Use the asset path (/content/dam/< name> .jpg) and the processingId (< id> ) shown in the log entry to correlate log errors with the specific asset in question.
    • You can also look up the processingId in the asset’s metadata within the JCR under /jcr:content/metadata/dam:processingId for further investigation.

  4. Ensure that ingested files adhere to supported formats for AEM Assets. Unsupported formats might result in processing failures.

  5. If possible, re-upload or re-ingest the problematic assets using supported configurations. Verify whether thumbnails are generated successfully after reprocessing.

  6. If issues persist despite verifying asset integrity and compatibility, escalate the matter to Adobe Support. Provide detailed information about affected assets and patterns in failures.

recommendation-more-help
3d58f420-19b5-47a0-a122-5c9dab55ec7f