Adobe Experience Manager: An Error Is Logged During the DAM Update Asset Workflow

Description description

When you upload an asset to AEM, an error may be logged in error.log while the DAM Update Asset workflow is running.

This article describes how to verify whether asset processing completed successfully.

Environment

Adobe Experience Manager 6.5 LTS

Adobe Experience Manager 6.5

Resolution resolution

If you can confirm the following, the asset processing can be considered to have completed successfully.

Check 1: Verify that the same error does not recur

Search error.log using the path of the affected asset and review the processing history.

After the initial error, if the workflow retries and the same error is not logged again, you can consider the issue resolved by the retry and assume that asset processing completed successfully.

$ grep "/content/dam/testfolder/test.png/jcr:content/renditions/original" error.log    *INFO* [ JobHandler: /var/workflow/instances/server0/yyyy-mm-dd/update_asset_1:/content/dam/testfolder/test.png/jcr:content/renditions/original]  ...    *WARN* [  ... Granite Transient Workflow Queue(com/adobe/granite/workflow/transient/job/var/workflow/models/dam/update_asset)]  org.apache.sling.event.impl.jobs.queues.JobQueueImpl.Granite Transient Workflow Queue Failed job Sling Job [  ... transient.workflowDataPayload=/content/dam/testfolder/test.png/jcr:content/renditions/original , ... event.job.retries=10, ... event.job.retrycount=1 ] , will retry 9 more time(s), retryCount=1    *INFO* [ JobHandler: /var/workflow/instances/server0/yyyy-mm-dd/update_asset_2:/content/dam/testfolder/test.png/jcr:content/renditions/original]  ...    *WARN* [  ... Granite Transient Workflow Queue(com/adobe/granite/workflow/transient/job/var/workflow/models/dam/update_asset)]  org.apache.sling.event.impl.jobs.queues.JobQueueImpl.Granite Transient Workflow Queue Failed job Sling Job [  ... transient.workflowDataPayload=/content/dam/testfolder/test.png/jcr:content/renditions/original , ... event.job.retries=10, ... event.job.retrycount=2 ] , will retry 8 more time(s), retryCount=2    *INFO* [ JobHandler: /var/workflow/instances/server0/yyyy-mm-dd/update_asset_3:/content/dam/testfolder/test.png/jcr:content/renditions/original]  ...

Check 2: Verify that the asset does not display an abnormal status in the Assets console

In the Assets console, open the affected asset in Card view:

https://< host> /assets.html/content/dam/testfolder

Verify the following:

  • The asset does not display a status such as Processing or Failed.
  • For a newly uploaded asset, the New badge is displayed and the asset is not in an error state.

Check 3: Verify that renditions have been generated

Open the affected asset in the Assets console. On the asset details screen, use the side rail to confirm that renditions have been generated.

https://< host> /assetdetails.html/content/dam/testfolder/test.png

recommendation-more-help
experience-cloud-kcs-help-kbarticles