@dpimpi-csm In my case the custom clientlibs were causing it to break, as the class names used for core components and custom were same and not unique.

@patricks1438961 You could probably consider these too-  https://github.com/TWCable/grabbit https://experienceleague.adobe.com/docs/experience-manager-65/assets/administer/assets-migration-guide.html?lang=en#migrating-between-aem-instances    

@rohankalra This could be a CSS issue with your custom component. Can you provide some more detail on the issue?

@AneleMzinyati it looks like there is a node with the same name, try giving a different name while saving queries. Sometimes it might persist in some past information, try clearing the cache and re-login too. 

@Kiranchonkar It could be due to firewall settings and the path might be blocked or related to maven version. https://backstage.forgerock.com/knowledge/kb/article/a15127846  

@neeraj_24412 Can you check the logs on the publisher, could be a permission-related issue for the user.

@kavalidurga You could probably use Random Participant Chooser step or Dynamic Participant Step; The Dynamic Participant Step component is similar to Participant Step with the difference that the participant is selected automatically at run time. https://experienceleague.adobe.com/docs/experience-ma...

Few query related details posted on- https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/dynamic-media-component-loading-dict-json/td-p/576534 for ref. 

@dh54220 You can just replace the .html with .model.tidy.json  similar to the sample wnkd site eg: .../content/wknd/language-masters/en/magazine.model.tidy.json  

@Shiv_Prakash_Patel You could use lazy loading to improve performance