Expand my Community achievements bar.

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

Unable to Exclude Locales During Rollout – Deselection Has No Effect

Avatar

Level 1

We're experiencing a problem with the rollout functionality where deselecting specific locales in the rollout dialog has no effect. Changes are still applied to all live copy pages, including those that were explicitly unchecked.

 

AEM Version: 6.5.13

 

Steps to reproduce:

  1. Visit http://localhost:4502/editor.html/content/we-retail/language-masters/en/experience.html
  2. Change some of the text in the hero (e.g: `Experiences` -> `Experiences Test`)
  3. Go to the rollout screen for the page
  4. Deselect rolling out to `/content/we-retail/ca/en/experience`
    1. Screenshot 2025-07-15 at 10.24.51.png
  5. Perform the rollout
  6. Visit http://localhost:4502/editor.html/content/we-retail/ca/en/experience.html
  7. See that the Hero text has changed even though that page was unchecked on the rollout screen
    1. Screenshot 2025-07-15 at 10.30.49.png

Expected results:

  • Only the selected locales should receive the updates. Unchecked locales should be excluded from the rollout.

When I look at the request that's made to the server, I don't see anything related to what's checked or unchecked in the payload. Do the checkboxes on the rollout screen actually do anything? If not, why are they there?

 

Screenshot 2025-07-15 at 10.27.51.png

 

Current Workaround:

To prevent updates to certain locales, we're currently skipping the rollout step and instead manually synchronizing only the live copies that should receive updates. However, this is inefficient since our typical use case is to roll out to most locales while excluding just a few. The deselect option in the rollout screen would be the ideal way to handle this, but it's not functioning correctly.

 

 

 

3 Replies

Avatar

Community Advisor

Hi @m900 ,

Can you verify If the specific paragraph component has any inheritance enabled on the live copy, you would need to break inheritance for that paragraph to prevent it from being updated from the master. 

Second thing that you can try is to de-sync the the live copy node by deleting the cq:LiveSyncConfig node.

Follow below article for more details:-
https://sourcedcode.com/blog/aem/how-to-re-sync-a-live-copy-language-root-to-a-blueprint-in-aem-msm#...

 

Hope it helps!

 

-Tarun

Avatar

Level 1

Hi @TarunKumar 

 

I'm aware of workaround options such as de-syncing and disabling inheritance. Ideally we'd be able to selectively rollout to specific locales from the rollout dialog using the checkboxes. Is that not an available feature? If not, what are those checkboxes for in the rollout dialog in this image?

m900_0-1752683786147.png

Avatar

Administrator

@m900 Did you find the suggestions helpful? If you need more information, please let us know. If a response resolved your issue, kindly mark it as correct to help others in the future. Alternatively, if you discovered a solution on your own, we'd appreciate it if you could share it with the community. Thank you!



Kautuk Sahni