Hi, Typically, the request headers visible through the browser’s developer console are sufficient for most debugging needs. The next step I would recommend is to check your local dispatcher. By setting the log level to DEBUG, you’ll be able to see the headers, as shown below. Finally, you can adjust...

Hey, check that actually your project-global-spa-react/components/xfpage inherits from "PAGE" (the resourceType you are adding in the adapter section). Please check this example of how the resourceType and relationship is handled in order for the delegation to work properly: https://github.com/adobe...

Hi, Did you try this https://blog.arborydigital.com/how-to-do-a-tree-activation-on-aem-as-a-cloud-service? Are yo using that same step?  

Hi,   The current preference is to use Cypress; however, you can still use Selenium if you need or want to. One of the older versions of the AEM archetype used Selenium as the default E2E framework. This is the commit that introduced cypress as the preferred framework: https://github.com/adobe/aem-p...

Hi, You need to use the delegation pattern to extend the model that is exporting the data and add your custom data. Then, you can use that data instead of the out-of-the-box (OOTB) data. You can check how to do this here:  https://experienceleague.adobe.com/en/docs/experience-manager-learn/getting-s...

Hey @bhavigoyal I took a look and it seems there is an issue with the context the Teaser component is using to render the anchors. You can open an issue in the core components GitHub or contribute with the fix[1]. As a workaround you can simple overwrite the href element with the proper context. Lik...

Hi,    You are missing the "filter" configuration in the dispatcher to allow the request flow till you AEM Publish instance, please check here how to set this configuration: https://experienceleague.adobe.com/en/docs/experience-manager-learn/sites/seo/sitemaps#dispatcher-allow-filter-rule  # Allow A...

Hey,Are you using ACS Commons by any chance? Maybe check if you are using any this: https://adobe-consulting-services.github.io/acs-aem-commons/features/http-caching-headers/index.html 

Hi,  Can you check if the below helps? https://www.youtube.com/watch?v=FeG74vpthig&ab_channel=DigitalExperienceWorkshop https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/assets/manage/smart-tags   

Hi,   If you're using AEM on-premise, you can disable the launcher that triggers the DAM Update Asset workflow, which is responsible for creating asset renditions.   Please refer to the following resources for more details: https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/ho...