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

Hi @Amir_khan4  As mentioned by @Magicr you can only use the Query to get unpublished assets and with that result set write custom logic to get the references if the assets in pages. You cannot combine both in one query Hope this is helpful.

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.    

Check the permissions that with which user you are downloading the assets. Error says not enough rights for https://samsclub.brand-portal.adobe.com/libs/sling/distribution/services/importers/default.   SO I suggest make changes to your permissions and try again.   Hope this is helpful  

Do you see any errors while restarting the bundle for these specific components ? If possible can you share the snippet of the code for event handler.  

Check out this blog for writing custom rollout configurations https://medium.com/exadel-digital-marketing-technology-practice/aem-experience-fragments-rollout-configuration-dd753369d4ec   Hope this is helpful.

If you the sling documentation for servlets, resolution happens with service ranking as well Please give your servlet with highest ranking in order to pick the default servlet https://sling.apache.org/documentation/the-sling-engine/servlets.html   Hope this solves issue

Could you please check the cron expression, if you have wrong expression you cannot see that in scheduler console Also check if all the Reference services are up and running Refer this sample example for end to end scheduler code https://aem.redquark.org/2018/10/day-13-schedulers-in-aem.html?m=1

That means every OSGi config needs to be committed deployed through the source control Refer to this as well, you will understand more on it.   https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/implementing/deploying/overview.html?lang=en#osgi-configuration