@Keerthana_H_N  We resolved this error yesterday for us. So basically what you have to do is following :  upgrade your node and Npm versions to node v14.17.5 and npm v6.14.14.delete node_modules in ui.frontendrun npm install to fetch packagesensure webpack works without issues locally. commit packag...

@Zhemchuzhnykov Check if you renditions generation is happening for your case. Better to check the error logs to see if there is any failure process step.

@nsvsrk  I came across a linkedin article where the author has made an attempt to come up with some guiding principles when it comes to AEM taxonomy. Have a look at this and may be this will help you in your quest     https://www.linkedin.com/pulse/mastering-tags-adobe-aem-practical-approach-boost-c...

@Shaheena_Sheikh This should answer your question - https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/aem-duplicate-launch-error/m-p/734484  

@dpkhmhs You can create a simple groovy script to copy these tags under the new path.  FYI, you will need JCR permissions to atleast create nodes to get this done. Check if there is a service user that you can use for this. If you dont have grrovy console installed in your environment, you can creat...

@NicholeVe You can try using AEM launches for this.  https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/sites/authoring/launches/overview  

@nbg19a Thread safety is primarily the main concern with getting the session by adapting the resolver.   A very good read on a very related topic by @joerghoh can be found here - https://cqdump.joerghoh.de/2013/07/23/cq-development-patterns-sling-resourceresolver-and-jcr-sessions/  

@SriramDhayal    What is the specific role of reference-adjustment-service in AEM, and in what scenarios does it get triggered? Reference adjustment service comes useful when you are migrating/moving your assets from one path to another. The resources where these assets are used would need to use th...

@san_11 You will have to convert the jars into an OSGI bundle. OSGI container needs bundles and not plain JARs.

@gvaem try  Authorizable publisher = userManager.getAuthorizable(workItem.getWorkflow().getInitiator());