DAM Metadata Writeback Workflow Triggering for SVG Files Despite Exclusion

[AnuragP13]

We are facing an issue with the DAM Metadata Writeback workflow in AEM. The workflow will be triggered for any metadata updates using launcher as shown below..

So we want to exclude SVG files from triggering this workflow as metadata writeback is not supported for SVG format. But even after writing condition for launcher for excluding svg files still this workflow is trigerring for svg files and eventually my workflow is getting struck in instances due to unsupported format for METADATA WRITEBACK

Expected Behavior:

- The DAM Metadata Writeback workflow should not trigger for SVG files once they are excluded in the launcher configuration.

Actual Behavior:

- Workflow still triggers for SVG files, causing unnecessary processing and potential errors.

Environment Details:

- AEM Version: [AEM 6.5.22]

- Deployment Type: [On-Prem]

Please advise on:

- Why the workflow is still triggering for SVG files despite exclusion.

- Any recommended configuration changes or patches to prevent this behavior

[VishalKa5]

Hi @AnuragP13 , 

Please refer below links,

https://experienceleague.adobe.com/en/docs/dynamic-media-developer-resources/image-serving-api/image... 

https://docs.adobe.com/docs/en/cq/5-6-1/workflows/wf-using.html#Starting%20Workflows%20When%20Nodes%... 

Thanks,

Vishal