Hi @arvind ,   here are some high-level details on how the dispatcher validates and caches secure content. Dispatcher determines that the requested content is cached and valid.Dispatcher sends a request message to the render. The HEAD section includes all of the header lines from the browser request...

Hi @anderspersson ,   Apart from the Splunk queries as mentioned by @Peter_Puzanovs , take a look at the feature introduced recently on cloud manager which allows you to see an overview of your usage. https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/implementing/using...

In that case, I will recommend bringing the content of the region affected to your local and doing the debugging. Also, check if you could set class-level logs to debug to get some more details.   Since it's 5.6 which is quite old, so there is no official support from Adobe on this version.  https:/...

Hi @manjunathdj ,   Check if you are using Sling Commons Scheduler in your codebase, it looks related to it. The use of Sling Commons Scheduler is not supported by AEM as a Cloud Service because it cannot guarantee to process when AEM environments are recreated, you could use Sling Jobs instead. htt...

Hi @Shivam153 ,   The main difference is in terms of requests being made to the server.   dependencies should cause your page to have extra requests to other clientlibs (external "subscribe") embed should "aggregate" those other clientlibs INTO the current clientlib (internal subscribe)   There is n...

Hi @avni27 ,   This looks like machine-specific limitations.   Here are a few things you could try:- Try to clear the browser cache, or try to open it in incognito.Free up some Memory/CPU usage on your machine.Try different browsers/machineCheck if you really need all of the content being parsed int...

Hi @rastogiashu1987 ,   Check if this user is also added to the product profile for that instance, more details here https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/onboarding/concepts/aem-cs-team-product-profiles.html?lang=en    Hope this helps!   Regards, Nitesh

I'm glad this helped to find the root cause.   For the documentation around the filtering on the dispatcher take a look here:- https://experienceleague.adobe.com/docs/experience-manager-dispatcher/using/configuring/dispatcher-configuration.html?lang=en#example-filter-section   For a working example,...

Hi @pixislinger , It represents the full-text search score of the node, which is a measure of the node's relevance to the full-text search expression.   More implementation details here:-https://docs.jboss.org/modeshape/2.6.0.Final/manuals/reference/html/jcr-query-and-search.html  https://lucene.apa...

Hi @rahul234dabas ,   Since this is an ajax call, check what error you see in-network tab. Also, since this is AEM as Cloud implementation check your dispatcher rules if the JSON is allowed to be served. If yes then check if it's blocked for this path.   Hope this helps!   Regards, Nitesh