metadata download issue after upgrade to 6.5.21

[ASP_Corp]

We are facing an issue after we upgraded to 6.5.21. earlier, when we download any asset, both OOTB metadata and custom metadata are downloaded along with the asset. when we open the asset (pdf), we can see the updated metadata. Now, in 6.5.21, the asset is getting downloaded, but only OOTB metadata is downloaded, the custom metadata is not, when we update the metadata, i see that the updated metadata node in crxde, but when i download the asset, i see only OOTB metadata and custom metadata is missing. iany ideas where i should look at? I don't see anything in the logs

so far i have zeroed in on workflows, i think the workflows got broken, we do have custom workflows, like update_asset workflow, but when the checked the update_asset workflow in /libs folder i dont see any changes in older and new 6.5.21 versions. i tried to re-run the workflow with the asset as payload, the workflow was a success, so iam a but clueless.

so, where do i get the logs for the workflow?, i mean if i use the log service in system/console, what class path should i point the logger to?

[narendragandhi]

Hi @ASP_Corp 

The XMP metadata write back process might have been broken post upgrade. Can you refer this documentation - https://experienceleague.adobe.com/en/docs/experience-manager-65/content/assets/administer/xmp-write... to confirm if these configurations are in place ?

Thanks

Narendra

[ASP_Corp]

Hi @narendragandhi and @giuseppebag , i tried these changes, but it did not work.

my observations : 1) In Adobe CQ DAM Rendition Maker configuration, progapagate XMP check-box was unchecked and when i checked on the instance that is not upgraded to 6.5.21 and where metadata is getting saved on download, there also the XMP check-box was unchecked. but i went ahead and checked the progapagate XMP check-box, but it didn't solve the issue.

2) i ran the logs on the debug at com.day.cq.workflow and com.day.cq.dam.core.process.MetadataProcessor (looks like it is modified to com.day.cq.dam.core.process.MetadataProcessorProcess) and com.day.cq.dam.core.impl.xmp.XMPMetadataExtractor. but no luck. i see only 2 writes in the logs.

18.03.2025 06:25:11.882 *DEBUG* [sling-threadpool-5bf1c270-956b-408e-a7a5-382247ccdee4-(com.day.cq.wcm.workflow.impl.wcmworkflowserviceimpl)-3] com.day.cq.workflow.impl.CQWorkflowService Creating GRANITE workflow session wrapper for user: wcm-workflow-service

18.03.2025 06:29:57.539 *DEBUG* [JobHandler: /var/workflow/instances/server0/2025-03-12/update_asset_47:/content/dam/xyzcompany/myregion/test/test_test/6521_issues/test-dr-030625_3.pdf/jcr:content/renditions/original] com.day.cq.dam.core.process.MetadataProcessorProcess remembering execution in workflow /var/workflow/instances/server0/2025-03-12/update_asset_47

[giuseppebag]

The missing custom metadata is likely tied to XMP writeback or workflow steps handling metadata extraction. Since your custom workflow runs successfully but doesn’t persist metadata, start by verifying if the MetadataProcessor step in your workflow (or any custom process steps) is correctly configured to include custom namespaces. 

From @narendragandhi suggestion pay attention to this sentence:

The feature writes back only those metadata properties that use jcr namespace, that is, a property named dc:title is written back but a property named mytitle is not.

For workflow logging, enable DEBUG logs for com.day.cq.workflow (workflow engine) and com.day.cq.dam.core.process.MetadataProcessor (metadata handling) via the OSGi log service. If XMP writeback fails silently, also enable com.day.cq.dam.core.impl.xmp.XMPMetadataExtractor. Test by updating an asset and monitoring logs for errors during metadata extraction/writeback.

[kautuk_sahni]

@ASP_Corp Did you find the suggestions helpful? Please let us know if you need more information. If a response worked, kindly mark it as correct for posterity; alternatively, if you found a solution yourself, we’d appreciate it if you could share it with the community. Thank you!

[ASP_Corp · Accepted solution]

I finally found out what is the issue. one of the workflow launchers using "DAM Metadata Writeback" has been deleted while upgrading to 6.5.21. don't know why this happened. Created a new workflow launcher with "DAM Metadata Writeback" fixed the issue.