@EstebanBustamante Yes mainly noticed for custom OSGI components, and yes it is reproducing locally as well.  

@aanchal-sikka it's with the same name, with different component ids-    

Hi Guys,   The code deployed is not getting reflected in our instances lately, not sure what is causing the issue all of a sudden.  We have observed there are duplicate component instances of the same implementation were getting created under -- .../system/console/components window.   As a workaroun...

@SupportMember The below thread seems something similar, it might help you - https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/content-fragment-template-leveraging-coral-datepicker-within/td-p/381803 

@thecqdeveloper1 May be this blog will help you, https://blogs.perficient.com/2021/08/11/server-side-rendering-using-adobe-io/ 

@Shardendu_Jha I believe It is not supported with the core AEM Assets product as of now.https://experienceleague.adobe.com/docs/experience-manager-65/assets/administer/assets-formats.html?lang=enDynamic Media is one way to use it as of now.

@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. 

@SupportMember Indexing would help in improving search performance, Probably load balancing strategies on publishers is an option as in your design it consistently hits the publish instances for each search result and can not be cached. 

@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.