Hi @AmitVishwakarma, Thanks for replying!If the DNS must necessarily point to Adobe CDN then why does the Customer managed CDN points to AEM managed CDN says "Point your CDN to the Adobe CDN’s ingress as its origin domain. For example, publish-p<PROGRAM_ID>-e<ENV-ID>.adobeaemcloud.com"It doesn't men...

yes @Asutosh_Jena_ the cqPageLucene-custom-1 is present as is.

Hey @Rohan_Garg, please check your inbox for the same! The approach #2 worked for us, I have also sent you the logs for the same.

Hi @konstantyn_diachenko.  We have defined the server name and aliases as below in vhosts fileServerName ${PUBLISH_ATMOSPHERE_HOSTNAME}The value is defined in cloud manager environment variables and it is picking the value correctly. 

Hi @giuseppebag, The other variables are defined in environment variable in cloud manager are giving expected value for xyz.comHowever, the case with this BRAND_HTTP is unique as it is defined in the custom.vars.We have removed the value defined in custom.vars to allow the environment variable value...

@ASHISHIBM  - This doesn't work it reflects the exact string as is -${env:BRAND_HTTP} 

Adobe support provided the below reply for this -The traversal was from product code that happened via a commit from our internal engineering.That query is unintended bug and our sites team removed the query entirely from the code-base.Fix for this will be available in the upcoming latest version of...

Hey @Rohan_Garg, if the table plugin is not styled with visible borders and cell separators natively then that's probably an improvement scope item but ideally they should not show this on the authoring dialog then - The style leads to some confusion as what you see on the dialog is not same to the ...

Hey @arunpatidar, I wasn't able to locate the custom CSS which would override the default CSS. The behavior is seen on vanilla instance too.We have added a custom clientlib to style as per our specifications for now. But there is scope of improvement in the styling here for the table plugin.

The problem is the launches are not getting promoted at their scheduled time!Our content authors set a time for it in AMS and at the scheduled time the launch was promoted.However in aemaacs, the launch isn't promoted, if we set the time manually again then the launch gets promoted.