Understand cq:LiveRelationship mixin on AEM assets

Assets in Adobe Experience Manager (AEM) show cq:LiveRelationship in jcr:mixinTypes even when the live copy option is hidden. This happens because AEM sets the property for MSM relationships at the repository level. Identify and remove MSM configurations for DAM content to stop this behavior.

Description description

Environment

Adobe Experience Manager (AEM) On-Premise 6.5

Issue/Symptoms

  • Assets under /content/dam show jcr:mixinTypes containing cq:LiveRelationship.
  • The Create Live Copy menu item is hidden in Assets Admin.
  • No visible MSM configuration node (cq:LiveSyncConfig) exists on assets.

Resolution resolution

To resolve this issue, follow these steps:

  1. Understand that AEM automatically adds cq:LiveRelationship to nodes that participate in an MSM live copy relationship, regardless of UI menu visibility.
  2. Recognize that this occurs when a DAM folder is or was configured as an MSM blueprint or live copy, or when MSM APIs or custom code establishes live relationships on DAM paths.
  3. Check for active MSM configurations under /content/dam by using a repository query tool to search for nodes of type cq:LiveSyncConfig.
  4. If configurations exist, review whether these live copies are still required and detach or remove unnecessary MSM configurations from affected folders after appropriate testing.
  5. Ensure no new DAM MSM relationships are created by reviewing custom code and processes that programmatically create live copies under /content/dam. Existing cq:LiveRelationship mixins on assets reflect past MSM relationships.
  6. After detaching or removing configurations, these mixins are no longer actively used.
  7. Verify that no further assets acquire the cq:LiveRelationship mixin by monitoring newly created or updated assets after the changes.

Notes:

  • Hiding the Create Live Copy option in the UI removes access to that action but does not disable MSM at the repository level.
  • Thecq:LiveRelationship mixin does not affect asset behavior unless an active MSM configuration exists higher in the hierarchy.
  • There is no global option to disable DAM MSM. Manage it through content structure changes and configuration cleanup.
recommendation-more-help
3d58f420-19b5-47a0-a122-5c9dab55ec7f