RolloutManagerImpl giving expected log output but not expected action

Question

Hi folks,First time using the JAVA RolloutManagerImpl. I'm creating a script to import a bunch of vanity URLs which need to be rolled-out to all markets. My code looking something like:RolloutParams rolloutParams = new RolloutParams(); // Setup internal-vanities market pagesfor (int i = 0; i < countries.size(); i++) { rolloutPages[i] = INTERNAL_VANITY_MIGRATION_PATH.replace("master", countries.get(i));}rolloutParams.master = internalVanityMigrationPage;rolloutParams.targets = rolloutPages;rolloutParams.isDeep = true;rolloutParams.trigger = RolloutManager.Trigger.ROLLOUT;rolloutManager.rollout(rolloutParams); Before running the page exists in master but not in the other markets. When running the log for RolloutManagerImpl gives me one entry which looks fine:10.07.2025 16:12:47.230 *DEBUG* [[0:0:0:0:0:0:0:1] [1752160367222] POST /bin/vanityurlmigrator.html HTTP/1.1] com.day.cq.wcm.msm.impl.RolloutManagerImpl Executing page rollout, params=RolloutParams, Main path=/content//master/en/internal-vanities, Trigger=rollout, Targets=[/content//gb/en/internal-vanities, /content//us/en/internal-vanities, /content//fr/en/internal-vanities, /content//it/en/internal-vanities, /content//de/en/internal-vanities, /content//row/en/internal-vanities, /content//ag/en/internal-vanities, /content//au/en/internal-vanities, /content//at/en/internal-vanities, /content//bs/en/internal-vanities, /content//bh/en/internal-vanities, /content//bb/en/internal-vanities, /content//be/en/internal-vanities, /content//bm/en/internal-vanities, /content//br/en/internal-vanities, /content//bg/en/internal-vanities, /content//ca/en/internal-vanities, /content//ky/en/internal-vanities, /content//cl/en/internal-vanities, /content//cn/en/internal-vanities, /content//hr/en/internal-vanities, /content//cy/en/internal-vanities, /content//cz/en/internal-vanities, /content//dk/en/internal-vanities, /content//eg/en/internal-vanities, /content//fi/en/internal-vanities, /content//gh/en/internal-vanities, /content//gr/en/internal-vanities, /content//gd/en/internal-vanities, /content//hk/en/internal-vanities, /content//hu/en/internal-vanities, /content//in/en/internal-vanities, /content//ie/en/internal-vanities, /content//il/en/internal-vanities, /content//jm/en/internal-vanities, /content//jp/en/internal-vanities, /content//kw/en/internal-vanities, /content//mx/en/internal-vanities, /content//nl/en/internal-vanities, /content//nz/en/internal-vanities, /content//ng/en/internal-vanities, /content//no/en/internal-vanities, /content//pl/en/internal-vanities, /content//pt/en/internal-vanities, /content//qa/en/internal-vanities, /content//ro/en/internal-vanities, /content//sa/en/internal-vanities, /content//sg/en/internal-vanities, /content//kn/en/internal-vanities, /content//lc/en/internal-vanities, /content//se/en/internal-vanities, /content//ch/en/internal-vanities, /content//za/en/internal-vanities, /content//es/en/internal-vanities, /content//tt/en/internal-vanities, /content//tr/en/internal-vanities, /content//tc/en/internal-vanities, /content//ae/en/internal-vanities] isDeep Am i missing something?Regards,Graham

SantoshSai · Accepted Answer

Hi @chebwin,I think, the issue not with the rollout() call, but with MSM configuration or my assumptions about the structure.The rollout() API does not create live copies - it only triggers a rollout on existing live copies of the master page. - If the target paths do not already have live copies mapped to your internal-vanities master, nothing will happen, even though the log shows it tried.Can you check - if rollout config actually attached to the master node?:Check /jcr:content/cq:rolloutConfigs under /content/master/en/internal-vanities and ensure it's correctly set.Also verify the live copies have a cq:LiveSyncConfig.Lastly, check Service User PermissionsRead access to the masterModify access to the targetsRights to execute rollout actions (wcm/msm/components/rollout paths)

Sign up

Login with SSO

Login to the community

Login with SSO

Scanning file for viruses.

This file cannot be downloaded