Hi @arunpatidar I had already tried these articles but nothing worked for me.

In AEM as a cloud, can we have multiple/custom variable files under conf.d/variables? We are on AEM 6.5 AMS currently and migrating to AEM Cloud. We have environment specific variable files like xyz_dev.vars, xyz_stage.vars etc. and a file like 002_init_xyz_vars.conf having an include statement like...

Hi @EstebanBustamante Thanks for your reply.We are using AEM as headless and consuming data from Publish instance only but we have a preview system (WCS) which is connected to our author environment to get all the pages which will be published at a later point of time.So, sometimes timeouts happen. ...

Hi @narendragandhi I had a look at the article but it says "AEM Author CDN caches immutable files, such as static assets that power the AEM authoring experience, and not authored content."We are using AEM as a headless and caching the API response. AEM Author CDN might not help here.

Hi @Madhur-Madan This is AMS. On AMS, we are already doing author caching but https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/implementing/conten... says we need to rename PUBLISH_DOCROOT to DOCROOT which only points to /mnt/var/www/html

Hi @Madhur-Madan  I am aware why we use author and publish instance.We already have dispatcher caching enabled on author on AEM 6.5 AMS due to some requirement.My only ask here is if author dispatcher caching is supported on AEM Cloud as well?

Is caching on author AEM cloud supported? I am working on migration from AEM 6.5 AMS to AEM Cloud. Currently, working on making the dispatcher changes cloud compatible. I am following the below link: https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/implementing/conten...

@Mayank_Gandhi Yes I have raised an Adobe Ticket for this.

@Mayank_Gandhi I am not manually changing the property. What I mean is, when we click on "Unpublish from Brand Portal", it automatically changes cq:lastReplicationAction property to "Deactivate". This should deactivate the asset from the publisher but it's not. So, ideally it should not change this ...

If the property, cq:lastReplicationAction is changed to "Deactivate" on Unpublish from Brand portal, then that respective asset should also be deactivated from the publish instance which is not happening. So, ideally it should not change this property.