Expand my Community achievements bar.

Submissions are now open for the 2026 Adobe Experience Maker Awards.
SOLVED

AEM MSM Custom Roll out Configuration

Avatar

Level 4

Hi ,

I am working on converting non MSM websites into MSM one, In that I have moved all my current site into language master, 

 

When I am rolling out , many unwanted pages also got rolled out like sand box pages which were not originally published before. 

I want to customize roll out action in such a way , that I need to see the replication status of the page and roll out accordingly. 

 

I tried following the approach mentioned in here https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/how-to-write-a-custom-roll... , it is not helping me much.

 

Is there any doc or method I could use to achieve the above requirement. 

Any leads are much appreciated.

 

Thanks,

Poovitha Selvaraj

Topics

Topics help categorize Community content and increase your ability to discover relevant content.

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Hi @PoovithaSelvaraj ,

In AEM MSM, the default rollout copies everything from the master to the live copies, which is why unwanted pages like sandbox content also get rolled out. To fix this, you need to create a custom rollout action that checks the replication (publish) status of each source page before rolling it out-if the page is already published, it gets copied, otherwise it’s skipped. This custom action is then added to a custom rollout configuration and applied to your live copies. In simple terms, think of it like adding a filter to the rollout process so it only copies pages that were actually approved and published, keeping test or draft pages out of your live sites.

Hrishikesh Kagane

View solution in original post

1 Reply

Avatar

Correct answer by
Community Advisor

Hi @PoovithaSelvaraj ,

In AEM MSM, the default rollout copies everything from the master to the live copies, which is why unwanted pages like sandbox content also get rolled out. To fix this, you need to create a custom rollout action that checks the replication (publish) status of each source page before rolling it out-if the page is already published, it gets copied, otherwise it’s skipped. This custom action is then added to a custom rollout configuration and applied to your live copies. In simple terms, think of it like adding a filter to the rollout process so it only copies pages that were actually approved and published, keeping test or draft pages out of your live sites.

Hrishikesh Kagane