@karthik-elumalai Could you please share the complete error log trail? I think there's more to it.

Hi @goyalkritika Please include those paths(/var/reports/../..)  in your filter.xml of ui.content   Thanks Bilal

Ah! that was the culprit. If you have not implemented a solution yet, I'd suggest you create a custom oak: index definition.   Thanks -Bilal

I'd suggest you to shuffle in your front end before showing the next items(when you click on show more).   So, fetch all the results and shuffle on every 'load more' click in your front end to make sure you achieve what's required.   Or you can utilise shuffle(): method from Collections library in J...

Hi @sateeshreddy    There's nothing called 'no sorting order' You either specify the order or by default it's sorted by jcr:score   thanks, Bilal

Hi @bagwanpankaj There's no way you can find out if a page is published to specific server/instance. For that you need to run queries in specific servers(publish) then probably reverse replicate to author and then index it based on what you get back.   Thanks -Bilal

Hi @akhilraj I was expecting specific issues you're facing while writing the GitHub action. Anyway, please let me know what did you try from your end and we can make it work.

Hey @sai2teja I'm assuming your dev and test servers are on linux/ec2 private cloud. I did this in my case   Create a shell script in your home directory of the aem server that would use the cURL to create backup content package for the filters you want.Add an expression in crontab of the server tha...

Hello, @MarkECis you need to run scripts/use groovy script/ACS commons on-deploy script to find out the asset references and update them accordingly as well when you're restructuring your dam assets   Thanks - Bilal

Hey @Tanika02 Followed this approach and this seemed to be the best so far however, in order to further lighten up the load on publish server I'm running the schedule job on author and publishing it. Thanks!