HI @Santhosh_Talepalle ,Can you check in chrome dev console if you see any error.ThanksTarun

Hi @Vani1012 , Please change enable property to false for below path in CRX:/etc/workflow/launcher/config/update_asset_create and /etc/workflow/launcher/config/update_asset_mod launchers configuration.Hope this helps!ThanksTarun

Hi @jayv25585659 ,Can you try CRX2OAK migration tool as it may help in migrating version across.You can follow below link for more details:https://experienceleague.adobe.com/docs/experience-manager-65/deploying/upgrading/using-crx2oak.html?lang=en ThanksTarun

Hi @robertol6836527 ,Are you getting the result in form of JSON, you cache the json file in AEM dispatcher or you can cache the entire page where the component is being used.

Hi @Uppari_Ramesh ,In path, can you trying passing the json resource that you might have loaded and also create specific nodes in the resource that you load. Lets see if that resolve your issue.

Hi @anasustic ,The error seems more likely from unclosed resource resolver. Can you check if you have derived it anywhere from resource resolver factory and not closed it?

Hi @KaibalyaJena_123 ,You should be able to apply the property when you select a single asset, this is the limitation from AEM side.

Hi @goyalkritika ,You can make use of Oak login token session expiration. The steps to do that can be found in the below linkHow to set the Oak login token session expiration | Adobe Experience Cloud

Hi @James_shan ,Can you try to run your aem jar with below command and check if its running fineFor ex: java -jar cq-author-4502.jar -Xmx1024m -XX:MaxPermSize=256m  

Hi @Aruna_surukunta_ ,If you are maintaining an external database then you would be having a data source configuration which represent the connection details of your database and Java class which actually runs a query.My assumption is that if you could write a query in your Java class to check for a...