@smithchar when you say global understanding is between projects if yes consider storing policies in locations such as /conf/global/settings/wcm/policies so that they are reusable across different projects/ templates. I never tried though but worth checking it 

@RajeevKu  then would suggest having pagination login in Java script and letting JS decide behavior based on the response object

you mean result is same as before when it was setup for 5 , What do you see on the console: success and error message?

@cxasha yes that is right

@jezwn @jezwn  it does support cloud service as well , https://opensource.adobe.com/asset-share-commons/pages/getting-started/set-up/ else think of creating a custom solution based on the Adobe assets api options  https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/as...

@RajeevKu consider belowGraphQL in AEM provides support for two types of pagination:limit/offset-based paginationcursor-based pagination 

@YashwanthPo  limitation as one journey at the time, considering using Condition before 1st journey ends and route to path 2 and path 3 , considering Path 2 depends on the imitated journey outcome 

@Selliers  i just tried, move in/out to folder works and not impact on the audience 

@MateuszRa  may be think of keeping your endpoint  behind the API gate way and let the gateway do access/validation/ etc  part and then route the request to actual API

@Mario248 set statefileslevel to zero , it would delete entire cache from root , right now it is 5 causing /checking cache at level 5 and your page seems to be not at  level 5