PDF asset processing delays in AEM as a Cloud Service
This article explains how to troubleshoot PDF asset processing delays in Adobe Experience Manager as a Cloud Service (AEMaaCS). PDF assets uploaded through the Assets HTTP API may remain in a processing state when unsupported rendition formats are returned or when processing ID mismatches occur during upload. To resolve the issue, correct rendition and processing ID errors.
Description description
Environment
Adobe Experience Manager as a Cloud Service (AEMaaCS), all versions
Issue/Symptoms
- PDF assets uploaded through the Assets HTTP API remain in the processing state (
dam:assetState ≠ processed) for significantly longer than expected, such as 40 to 60 minutes instead of less than 2 minutes. - Custom publishing queues remain blocked while waiting for the asset state to transition to processed.
- Asset processing logs contain errors such as rendition_failed: RenditionFormatUnsupported and references to incomplete renditions.
Root Cause
AEM does not transition the asset state to processed when unsupported rendition formats are returned, causing the system to wait for renditions that cannot be generated. Processing delays also occur when multiple or mismatched processing IDs are associated with a single asset upload, causing AEM to treat renditions as incomplete.
Resolution resolution
Follow the steps below to resolve the issue:
- Review the asset processing logs for affected PDF assets. Look for entries that contain
rendition_failed: RenditionFormatUnsupportedand check for references to incomplete renditions or multiple processing IDs associated with a single asset upload. - If multiple processing IDs exist for the same asset upload, investigate the upstream system or integration for duplicate or conflicting upload requests. Ensure that each asset upload uses a single, consistent processing ID.
- If an asset remains in a non-processed state for an extended period, manually reprocess the asset to reset its state. Alternatively, wait for the system timeout mechanism to reset the state automatically.
- Continue monitoring asset processing logs for similar symptoms during future uploads.
- If the issue recurs with a single processing ID and assets remain in the processing state, collect detailed logs and contact Adobe Support for further investigation.
- Verify the resolution by confirming that PDF assets transition to the processed state within the expected timeframe and that publishing workflows are no longer blocked.