Hello , The build/deploy should work fine if we have only one config per PID across all the runmode configs. Please check by removing duplicate configs. Regards,Anubha

Hello Vikash, You can refer consoles - /system/console/slingevent and /system/console/events to view details of these failed sling jobs. Regards,Anubha

Hi Kusuma,You can refer below document for your query , see section : Using a custom Replication Agenthttps://helpx.adobe.com/experience-manager/using/aem64_replication_api.htmlRegards,Anubha

Hi Sunil,As per me sorting works only for List view. The fix given by me is only for List view.

Hi Sunil,Can you try to overlay columns [1] to switch 'sortable' to 'true' and make columns sortable in List view. In your case if you need to sort by name - update sortable property to true for [2] node.[1]/libs/dam/gui/content/commons/availablecolumns[2]/libs/dam/gui/content/commons/availablecolum...

Hi Subrato,What happens when you remove this property ? Did the functionality work for you.Also did you see anything in debug logs for API : com.day.cq.wcm.msm , to check the sequence what is happening.

Hello,The issue stands fixed in AEM 6.3.3.0.In case you are still facing this issue on AEM 6.3.3.2 , I would request you to please open a daycare case with Adobe and provide all the details so that team can verify the behavior on it.

Hello,This issue stands fixed in AEM 6.3.3.0 via NPR-24177. This was reported for AEM 6.3.2.2 .What is the exact version of AEM you are using?Regards,Anubha

Hi Indra,Please compare the configuration: Day Cq Link Checker Service on your pre prod environment with your QA environment.You can also test resolving the link by using the URL : http://localhost:port/system/console/jcrresolver