@Sanjana12 you can use pagination from the front-end using JS based on the json result from the backend logic. sample example for ref. http://jsfiddle.net/Lzp0dw83/ Hope this helps.

@user17427320 seems this is addressed here ref.  https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/error-while-creating-a-custom-rollout-option/m-p/442355  

@VuongNguyen You could probably use a unique id as a query parameter for each user on the url , which will force the url to not cache and hit the server, in case there is some caching involved.

@Tessa_learner1 you can ref. these- https://experienceleague.adobe.com/docs/experience-manager-65/assets/dynamic/administering-dynamic-media.html?lang=en https://experienceleague.adobe.com/docs/experience-manager-65/assets/dynamic/config-dms7.html?lang=en  

@manishaa5646486 Can you elaborate a bit more, on what exactly are you trying here?

@annkitaaggarwal Seems like the instance is corrupted/ instance was terminated abnormally, You would probably need to create a fresh crx-quickstart folder. you can use also make use of backup and restore, proabably will be useful in such situations- https://experienceleague.adobe.com/docs/experience...

@ChaoXiong You can use the "Add rule" and choose "inlcude" from the dropdown and add your filter- for eg. something like this: Hope this helps.      

@Farnsbert You can use limit query and pagination logic if the results are too large. You could have a custom OSGI configuartion to set the limit value for the query used. Not sure what exactly is the use case here, but hope this helps.

@NehaCMS Probably this thread will help you with some insights: https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/dispatcher-evicted-cache-items/m-p/438851