Automatic live copy in experience fragment

Hello ​@anurag_dang 

In AEM as a Cloud Service, there is currently no out-of-the-box Experience Fragment workflow that matches the automatic live-copy creation behaviour you see with Sites pages.

For Sites, AEM provides specialized MSM/site-creation capabilities for building multilingual site structures. For Experience Fragments, Adobe documents MSM support, but the supported model is based on creating live copies and then using rollout/synchronization, rather than automatically creating locale live copies the moment a new XF is authored in language-masters.
Sources:

• MSM Best Practices
• Reusing Content - Multi Site Manager and Live Copy
• Experience Fragments

The recommended pattern is to:

1. Set up the desired XF live-copy structure for the relevant branch/root.
2. Use MSM rollout/synchronize to propagate updates from the source XF structure to the corresponding live-copy structure.

In other words, Experience Fragments support MSM, but they do not currently provide the same automatic site-style live-copy provisioning behavior that exists for Sites page structures.
Sources:

• Reusing Content - Multi Site Manager and Live Copy
• Experience Fragments

If full automation is required

If the requirement is to have new XFs automatically create locale live copies with no author action, that would generally require a project-specific customization rather than standard OOTB behavior. Adobe's MSM guidance is to keep customization minimal and carefully governed.
Sources:

• MSM Best Practices

Hello ​@anurag_dang , any updates?

Hi ​@anurag_dang 

This is a known gap between Sites and Experience Fragments in AEM Cloud and you’re not alone in running into it. The Adobe Employee’s explanation is correct XFs don’t get the automatic live copy provisioning that Sites pages do out of the box.
What’s worked well in practice for teams that need something closer to automatic behavior is combining an MSM rollout configuration with a custom workflow or launcher. You set up a workflow launcher that triggers on XF creation under language-masters and then kicks off a rollout to the live copy roots automatically. It’s not pure OOTB but it’s a clean, supportable pattern that doesn’t require heavy MSM customization.
The rough setup looks like this create a workflow launcher that watches for node creation matching the XF content type under your language-masters path, then in the workflow model run a Rollout step pointing at your configured live copy targets. The first time you author an XF in language-masters it triggers the launcher which creates the live copy structure automatically.
One thing to watch out for is that the rollout config on your XF root needs to include the LiveRelationshipManager actions you want specifically page creation, not just content sync otherwise the rollout will try to sync into a live copy structure that doesn’t exist yet and silently do nothing.
If full automation without any workflow overhead is the requirement, the cleanest long-term approach is raising it as a feature request with Adobe since this is a genuine gap compared to Sites behavior and there’s enough demand in the community that it would be worth tracking.

Hi ​@anurag_dang 

Since there is no simple configuration toggle for this, the easiest, no-code way to automate it is using a Workflow Launcher.

Here’s exactly how to set it up so it works cleanly without bogging down your system:
 

Create a Custom Workflow Model

Create a simple workflow with a single step: the standard WCM Rollout process step.

• Configure the arguments in this step to use your specific rollout config (e.g., standard rollout).

Configure the Workflow Launcher

This is where you have to be precise. If you set this up too broadly, you will cause infinite loops.

• Event Type: Created

• Node Type: cq:Page (Remember, AEM stores XFs as pages under the hood).

• Path: /content/experience-fragments/myProject/language-masters(/.*)?

• Workflow: Point it to the custom model you created in Step 1.

Keep your path restriction strictly tied to language-masters. If you just listen to the whole /content/experience-fragments tree, the act of creating the live copy will re-trigger the launcher, creating an infinite loop that will crash your instance.
Your rollout config must include actions that create pages, not just sync content. Otherwise, if the live copy folder structure (/en_US/) doesn't exist yet, the rollout will silently fail.

If your requirements grow and you want a more robust, code-based approach later, you would need a Java developer to write an OSGi Event Handler (ResourceChangeListener) that passes the path to a Sling Job, using the LiveRelationshipManager API to establish the links programmatically. But for a quick, native fix, the Workflow Launcher is the way to go.

Thanks

Partyush