Hi @Zendark Using JS I believe you can do something like:const bodyParts = new URLSearchParams(); bodyParts.append(':operation', 'activate'); bodyParts.append(':path', '/content/my/page'); fetch('http://localhost:4592/bin/replicate', { method: 'POST', headers: { 'Content-Type': 'app...

Try to lookup online resources on how to include third party dependencies:https://myaemlearnings.blogspot.com/2021/08/embedding-third-party-dependencyosgi.htmlhttps://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/how-to-use-third-party-api-in-aem/td-p/553767https://experienceleag...

You need to clear apps in order to avoid configs overlapping. Keep only one config for the workflow purge, the one from your codebase.

I mentioned it in my comment before my last one, at point 2. If you want to dig more , you can start with this Adobe documentation:https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/headless/introduction. It explains the authoring journey in the headless context.

I would say you would need to write logic to expose json containing component data.So the most basic example for a core component, for example Carousel one, would look something like: <div data-sly-use.carousel="com.adobe.cq.wcm.core.components.models.Carousel" data-something="${carousel.data.jso...

As I said, depends on a lot of things. But to put that in numbers, for example I have seen the following two project setups (strict in terms of AEM developers team): Project 1: 4 AEM developersAEM on-prem> 10 git repositories~ 100 AEM components2 templates10 integrations with external systems1 relat...

Request for Feature Enhancement (RFE) Summary:AEM References ManagerUse-case:Track references and control changesCurrent/Experienced Behavior: It is very common situation when for example an AEM component definition gets changed and the changes immediately need to be reflected on the content. For ex...

Hi @kchaura I am sure you have config files in order, but just to be sure, how does your osgiconfig folder looks like ?  

As it has been described in those articles also, you basically need to expose your AEM data to the Microfrontend components. It depends on the architecture (headless vs headfull vs hybrid) of course. You can understand more from this article: https://medium.com/@prajwaljainkmt/aem-architecture-headf...

Hi @Tom_Fought All the indications from @narendiran_ravi are very good and are first things to go to in such cases. In addition I would add that when I experienced such issues, for me it was because two things:1. I had long running jobs that were continuously writing data. Maybe you have some custom...