Standard Rollout Config not updating content in live copy after rollout | Community
Skip to main content
L
LK-CMS
Level 2
March 19, 2025
Solved

Standard Rollout Config not updating content in live copy after rollout

  • March 19, 2025
  • 3 replies
  • 788 views

Hi,

 

We have discovered an issue where even after rolling out a folder from global level to livecopy, status is successful but content fragment in folder is not updated with the content of global content.

 

Before rolling out, all the folders in the live copy were installed from dev to uat using package manager. Post that, we observed below details.

 

AEM Cloud UAT Environment 

Content fragment global path - content/dam/project/language-masters/en_us/brand-copy/address/activation

Live copy path - content/dam/project/en_us/brand1/address/activation

 

Global Content fragment - Created on Feb 28, 2024 and Modified on August 28, 2024

Live Copy Content Fragment - Created on Nov 19, 2024 and Modified on November 8, 2024

 

My query is are the above timestamps causing the content not be updated in live copy due to the fact that live copy date modified is later to that of global?

Or is there any other issue when rolling out content fragments using stand rollout config that I am missing here. 

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by LK-CMS

Thank you @kedar0910 @arunpatidar @giuseppebaglio for responding and helping out.

 

After lot of analysis, we found out the below.

We transferred the content fragment from dev environment live copy into uat live copy using package manager. Due to this live copy cq:lastRolledout is 11th Feb ruary 2025 but language master cq:lastModified is 28th August 2024. So, live copy is younger than language master and hence AEM isn't rolling out or skipping to update. Let me know, what would could be the best way to avoid these situations.

3 replies

kedar0910
kedar0910
Level 2
March 19, 2025

make sure if the live copy content (jcr:content) node has jcr:mixinTypes property with cq:LiveSync value. 

L
LK-CMSAuthor
Level 2
March 19, 2025

I checked jcr:content for livecopy and jcr:mixinTypes has these values cq:LiveRelationship, cq:ReplicationStatus2

Also checked other livecopy fragments where roll out is working and value of jcr:mixinTypes is same.

arunpatidar
Community Advisor
arunpatidarCommunity Advisor
Community Advisor
March 20, 2025

Hi @lk-cms 

Can you also check the jcr:content/cq:LiveSyncConfig node in your live copy root? Specifically, look for the exclude property to see if the Content Fragment is excluded from the rollout.

If CF is not excluded, please try resyncing it again.

Arun Patidar
    giuseppebaglio
    giuseppebaglio
    Level 10
    March 20, 2025

    The name of the property to exclude is likely "cq:excludedPaths."

     

     
      L
      LK-CMSAuthorAccepted solution
      Level 2
      March 21, 2025

      Thank you @kedar0910 @arunpatidar @giuseppebaglio for responding and helping out.

       

      After lot of analysis, we found out the below.

      We transferred the content fragment from dev environment live copy into uat live copy using package manager. Due to this live copy cq:lastRolledout is 11th Feb ruary 2025 but language master cq:lastModified is 28th August 2024. So, live copy is younger than language master and hence AEM isn't rolling out or skipping to update. Let me know, what would could be the best way to avoid these situations.

        kedar0910
        kedar0910
        Level 2
        March 21, 2025

        one option i can think of is, to disable this OOTB workflow "DAM Set last modified date" , before you do content sync, that way it doesn't update the last modified date. 

          Terms & ConditionsAccessibility statement

          Loading footer...