Thanks for the replies, we have figured out the issue- it was due to the scope defined in the maven dependency, we had to change from compile to provided in the pom file.

@Tessa_learner1 In short,  Node is like a unit of the JCR repository and resource is something that sling uses to access Nodes. JCR APIs act on the Node and Sling APIs use the resource.   The Sling API works at a higher, more abstract level than the JCR API. This allows your code to be more reusable...

@RobertHarperFS it seems by default, the ability to switch to the classic UI via the admin consoles has been disabled,  ref. https://experienceleague.adobe.com/docs/experience-manager-65/administering/operations/enable-classic-ui-admin.html?lang=en  

@maheshp  1. You could create a utility that updates the page properties in bulk. 2. You could make use of groovy scripting    you could have a look at this ref. too- https://github.com/AdobeDocs/experience-manager-65.en/blob/main/help/sites-developing/bulk-editing.md https://experienceleague.adobe....

@DPrakashRaj Only one bundle instance 

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

@AEMWizard 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/