jcr:title and jcr:description is not getting sync when I use OOTB rollout in cloud sdk

Some properties are exluded by default in Multi-Site Manager (MSM), thus they are  not synced.

Try this:

1. Modify the regular expression in the OSGi configuration (CQ MSM Content Update Action - com.day.cq.wcm.msm.impl.actions.ContentUpdateActionFactory) to include your custom property.

   For example, to include cq:styleIds, change the regex from:

   cq:(?!(designPath|template|lastTranslationUpdate|targetEngine|robotsTags)$).*

   to:

   cq:(?!(designPath|template|lastTranslationUpdate|targetEngine|robotsTags|styleIds)$).*

2. Add the updated configuration to your deployment pipeline for cloud environments as shown below:

   cq.wcm.msm.action.excludedprops = [
     "jcr:.*",
     "sling:(?!(resourceType|resourceSuperType)$).*",
     "cq:(?!(designPath|template|lastTranslationUpdate|targetEngine|robotsTags|styleIds)$).*",
     "publishCampaignId"
   ]
   

    

3. Deploy and verify changes in the development environment.

4. Roll out again and verify the property synchronizes correctly across all live copies.

More information:
https://experienceleague.adobe.com/en/docs/experience-manager-65/content/sites/administering/introduction/msm-sync?lang=en#excluding-properties-and-node-types-from-synchronization

https://experienceleague.adobe.com/en/docs/experience-cloud-kcs/kbarticles/ka-27312

​@JakeCham -

If jcr:title / jcr:description aren’t syncing via MSM, it’s usually not due to explicit OOTB exclusion. The first thing to check is whether inheritance is broken on the live copy—if those properties were modified locally, MSM won’t overwrite them during rollout.

Since nothing exists under /apps/msm, you’re using the OOTB rollout configs from /libs/msm/wcm/rolloutconfigs, which is expected. Also, MSM doesn’t define property-level rules in rollout configs—it works via sync actions.

If inheritance is intact and the issue still persists, it’s worth checking the OSGi config for com.day.cq.wcm.msm.impl.actions.ContentUpdateActionFactory to see if any excluded property patterns have been customized.

No need to raise an Adobe ticket—this is standard MSM behavior and is typically resolved through inheritance or configuration checks.

Hi ​@JakeCham 

 

Question 1: Why are jcr:title and jcr:description not syncing with OOTB rollout, and how to add them?

• This is expected OOTB MSM behavior.

• After a Live Copy is created, page metadata like jcr:title and jcr:description is treated as author‑owned and is not re-synced on subsequent rollouts.

• These properties are not excluded via an obvious excludeProps rule, but are skipped by the internal MSM rollout logic.

Adobe ticket is not required.

Hey ​@JakeCham 

1. Verify 

   cq:propertyInheritanceCancelled

    on the live copy page's 

   jcr:content

    — this is the #1 cause.

2. Try a manual rollout from the blueprint and check if the properties sync.

3. Check if the live copy was created with 

   deep=false

    or if the relationship is detached.

4. Review AEM error logs during rollout for any MSM-related exceptions.

Only raise an Adobe ticket if you've confirmed inheritance is intact, no custom exclusions exist, and the properties still don't sync , that would indicate a potential platform bug.