@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  

CJA is not just a web channel, segments would be more or less similar to AA if CJA was based on the AEP unified/stitched profile [assuming it has a Web channel / AA ]  @DineshPrasanth 

@DhanA2  look in Sessionization Settings that might help

@KUMAR any error on the logs and explore below?- Asset file size and type [supported or not]- asset microservice /- processing profile config :  Tools > Assets > Processing Profiles. Click Create.- try to upload using he POST request is POST https://[aem_server]:[port]/content/dam/assets/folder.init...

@HariPr6  think of using dynamic media API capabilities and a custom solution to address your use case - https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/assets/dynamicmedia/dynamic-media-open-apis/dynamic-media-open-apis-overview 

@imalakaamir consider to use the below with regular express - mod_rewrite  : for URL rewrite and RewriteCond to capture/rewrite URL-with param  

@JakeCham  adding to @arunpatidar  inputs, approach should be centralized for assets to manage end to end asset life cycle for organization and Adobe DAM provides/ support all the use cases  of internal / external use of assets