I think refresh page is not proper solution to handle something like this How many pages will you refresh and which user page will be refreshed? Can you explain the what type of Metadata how frequently this will happen based on that we can think of solution

Below thread explains on the permissions that needs to /conf folder, could you please check if you have enough permissions to read the resource. If not provide the required permissions and restrict it through the dispatcher. https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/a...

Can you check which resource is passed to the method while calling the from scheduler ? Check if both the resources are same in On-demand and from scheduler.    

Is the en is your master? Or every locale have different page count other than en? Can you also explain more on the comparison clearly?

AEM just maintains the pointers to binary storage for the Assets uploaded, Please refer the below screenshot from the documentation.

Hi @pixeldvx ,   Check this article which explains step by step to have custom styles added to the component. https://experienceleague.adobe.com/docs/experience-manager-65/authoring/siteandpage/style-system.html?lang=en   Hope that helps!!!

Do you have any page properties which identifies the locale and language information, if not have some configurations on the root level and read them in your code using inherited page properties, then try to form the path dynamically, this should you path dynamic and query to be executed dynamically...

Hi @gargkrishna  This article explains writing JUNITS for sling model and as well to servlet class refer this to get more information. https://taylor.callsen.me/unit-testing-aem-sling-models-and-servlets/ Hope it is useful.

1. Write servlet which is common to all the filter  Ex: /aem/search/servlet 2. Servlet should be responsible for capturing the type of filter user selected (filter1, filter2) 3. Based on the filter/filters selected have a service with different query builder queries. 4. Map the result back to UI   B...

If the data is in AEM using querybuilder API with proper indexed data should work fine. Make a custom servlet which call the different service layers depends on the filter and retrieve those back to front end as JSOn object and make every subsequent call be an asynchronous call to the servlet.