Hello @samara271, From your explanation, I assume a previous build (and deployment) was successful on the same code base and no config change has been made after that. In such case you can do that following:-  you can raise support ticket to ask Adobe to look into it -  for future, you can keep an e...

Hello @akhilraj, There is no direct command to restart the AEM instance using curl: https://experienceleague.adobe.com/docs/experience-manager-65/administering/operations/curl.html?lang=en#common-operational-aem-curl-commands However, since you are using Github CI/CD runner instance, you have the op...

Hello @Ganthimathi_R, I believe you are using the updated AEM archetype, there (pom.xml under ui.apps.structure module) you have the option to put the list of valid roots (JCR Paths) that you want to work on as following:   <build> <plugins> <plugin> <groupId>org.apache.jackrabbit</group...

Hello @KaibalyaJena_123, Try this:http://localhost:4502/content/dam/image-path/image-name/jcr:content/renditions/original if you are generating the path problematically you need to know the actual image-path including the image-name.  Thanks 

Hello @ABINESH76, The snippet you provided is just a part of the error message. Look for the full error message in your build log. It should provide more details about the specific problem. Sometimes, build errors are caused by issues with project dependencies. Make sure that your project's dependen...

Hello @annkitaaggarwal, Commenting out the dispatcher module from pom.xml is not enough, please make sure that the dispatcher module is removed/deleted from the code base (the one that is getting deployed through cloud manager). Though its recommended to push the dispatcher config changes via cloud ...

Hello @TrifaCh, Please check if there is any cq:EditListenersConfig within the component. If so, that can be the reason of possible refresh after edit. You can remove it to stop the refresh, and then you can debug your custom code for the component. when you debug look for any possibility of infinit...

Hello @sreenu539, I managed to upgrade the AEM version to 6.5.17 without any issue.Please make sure you follow the steps recommended by Adobe: https://experienceleague.adobe.com/docs/experience-manager-65/release-notes/service-pack/6.5.17.html?lang=en#install Thanks 

Hello @sspatra25, I see both the command install node and npm and npm install getting skipped in the log. Is that the same for local build as well?  Can you check if are you using the same node version mentioned in the pom.xml for development locally? Can you also add --no-cache with npm install and...

Hello @sspatra25, It looks like something to do with the node version and dependencies. Is that intermittent? Is that running successfully locally? Thanks