Assets stuck in pre processing state after upload in AEMaaCS
In Adobe Experience Manager as a Cloud Service (AEMaaCS), assets uploaded through the Workfront connector or manual upload remain in the pre-processing state and don’t proceed to full processing. To fix this issue, restore the asset processing workflow so assets transition from pre-processing to processing.
Description description
Environment
Adobe Experience Manager as a Cloud Service (AEMaaCS), all versions.
Symptoms
When assets are uploaded to AEM via the native Workfront connector or by manually uploading multiple images, the assets may remain in the PREPROCESSING state for an extended period and do not automatically proceed to further processing steps.
Expected workflow
A healthy asset processing workflow typically follows these states:
PREPROCESSING→ malware-scan job submitted- Asset Compute completes malware scan → Completing pre-processing action (
result=SUCCESS) - State changes to
PROCESSING→ full rendition job (thumbnails, metadata, etc.) submitted - AEM completes all renditions →
CUSTOMWORKFLOWPROCESSING→PROCESSED
Cause
The issue occurs when the asset processing workflow does not complete the transition from PREPROCESSING to PROCESSING, even though the malware scan job finishes successfully. This prevents the asset from moving forward to rendition generation and final processing.
Resolution resolution
Follow the steps below to resolve the issue.
- Check the processing status of the affected assets in the AEM Assets UI.
- Review the logs for the affected assets to confirm whether they are stuck in the
PREPROCESSINGstate and whether the malware scan completes without aresult=SUCCESSentry. - To manually resolve the issue, navigate to the affected asset(s) in AEM Assets.
- Right-click the asset and select Reprocess Assets from the context menu.
- Monitor the asset status. Processing should complete within 2–3 minutes.
- If the issue recurs, collect the relevant logs and asset details, and contact Adobe Support for further investigation.