Currently, I am facing an issue in MSM service on content activation. Any help would be helpful.
Issue - The live-copy contents are getting published automatically whenever there is a change in BluePrint source content without any manual activation. I have given the trigger as 'publish'. But it triggers on any content modification itself. No customization has been done so far. As of now, I am using the core service.
Expectation: The live-copy content should be activated only when there is a publish trigger in the source blueprint page.
Path to check rollout configs as mentioned by Vishu:
/content/<we-retail or your project_root>/us/en/jcr:content/cq:LiveSyncConfig
Can you try with OOTB "Activate on Blueprint activation" config and see how it goes?
Currently, I am using all the OOTB rollout configs. Not added any of my custom ones. Please find the config screenshot.
The OOTB 'Activate on blueprint activation' is causing the issue. It activates the live copy pages without any publish trigger. I have checked the cq:trigger for 'Activate on blueprint' roll config. It looks correct and mentioned as 'publish'.
According to this, the content from blueprint (Source) will get copied to live copy automatically when there are any modifications in source and livecopy will be activated/deactivated only when the source is activated.
But in your case, the live copy is getting activated without the activation of the blueprint. Is my understanding correct?
yes. you are right. It is not working as expected.
The activation is happening without the activation of the blueprint pages.
Thanks for the clarification.
We would need debug logs and more information in order to investigate this issue further. Please open a daycare ticket  and share the error and debug logs.
For Debug level MSM log:
- Click Add New Logger
- Set it with this configuration:
Log Level: Debug
Log File: logs/msm.log
Not directly related to your problem: "Push on Modify" is likely to overwhelm AEM instances, and I would not recommend it when the number of livecopies exceeds a small number.
Thanks Gaurav for your suggestion. As mentioned in the other thread, the dispatcher flush configuration was causing the issue.