Hi @spidey1405  Use following APIs for Replication on Cloud Service https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/operations/replication.html?lang=en#replication-api  

@Nikhil-Kumar Try validating from below Code Snippet https://engineering.icf.com/aem-content-fragments-as-an-api/#:~:text=Creating%20a%20content%20fragment%20API   If it is still not resolved, kindly share your Code Snippet

@akshaybhujbale  Felix Console, is no longer accessible on AEMaaCS.   However, you can explore alternative ways to achieve your goal, please find them below:https://experienceleague.adobe.com/docs/experience-manager-learn/cloud-service/debugging/debugging-aem-as-a-cloud-service/developer-console.htm...

I am afraid, that should be not the case. New branch should not be created evrytime   Ideally, development sprints or stories should be committed in Feature Branches.  Developers would commit their stories or defects in their respective Feature Branches. End of a Sprint, these branches are merged in...

@rgravisankar  Hope you have configured your CI/CD Pipeline with Deployment Trigger as "On GIT Changes" Can you add a screen shot of your CI/CD Pipeline Configuration and provide more info on your GIT Branching Strategy?While below link might help you to verify the configuration for automatic deploy...

Hi @Ashwin_Raju  In my opinion the best way to implement any action on a Publish Event, is using Sling Events. Resource ChangeListeners are more for Resource Change Events. Eg, creating, modifying and deleting a Resource.   Please find below link to find out preferable listeners for different events...

I believe its just a warning and would not fail your build, if you use  com.day.cq.wcm.api.NameConstants However, this issue might get fixed in the next set of releases for AEM SDK.   @janiwe  

You mentioned that replication is successful, so it cannot be an issue of blocked Replication Queues.   Also, as per above Code Snippet, you must be using Job Consumer.  Can you refer below Code Snippet, and see if you haven't missed anything. Also, please put loggers inside Job consumer, logging st...

@Vinit_Pillai  Possibility is, the event handler is taking too much time to execute. If this time goes beyond 5 secs which is default TimeOut value, then the handler would be blacklisted and would never execute.   Hence, please consider using Sling Jobs or Job Consumer which will guarantee execution...

Guarantee is a trick word to suggest.  AEM supports and provide features to its users to design and build such a Website that helps to meet the WCAG guidelines.    You might have to undergo multiple cycles of Accessibility testing to be sure that your website conforms to these guidelines.