DocumentationExperience Cloud KCS

Remove orphaned Dynamic Media cloud configurations in AEM as a Cloud Service

Last update: October 2, 2026

This article explains how to identify orphaned or duplicate Dynamic Media cloud configuration nodes in Adobe Experience Manager as a Cloud Service and outlines the steps to request their removal when they cannot be deleted through the UI or CRXDE.

Description description

Environment

  • Adobe Experience Manager Assets as a Cloud Service
  • Dynamic Media (Scene7) cloud configuration
  • Configuration nodes under /conf/global/settings/cloudconfigs/

Issue/Symptoms

  • You find multiple Dynamic Media configuration nodes under /conf/global/settings/cloudconfigs/.
  • The active configuration, such as dmscene7, shows a Scene7 company icon or thumbnail and a recent modification date.
  • Other nodes, such as dmscene72 or dmscene73, have a blank icon, no thumbnail, or an old modification date.
  • You can’t remove the orphaned nodes through the AEM interface, and CRXDE is read-only in this production environment.
  • Dynamic Media synchronization or publishing is inconsistent.

Cause

Failed or incomplete Dynamic Media configuration attempts can leave orphaned or incomplete nodes under /conf/global/settings/cloudconfigs/. In the reported scenario, multiple configuration nodes make it difficult for AEM to determine which configuration to use, which can lead to synchronization or publishing inconsistencies. Confirm which configuration is active before requesting cleanup.

Resolution resolution

Follow the steps below to resolve the issue:

  1. Identify the active Dynamic Media configuration:

    • In AEM, open Tools > Cloud Services > Dynamic Media Configuration.
    • Identify the connected configuration, such as dmscene7, by its Scene7 company icon or thumbnail and recent modification date.

  2. List the sibling configuration nodes under /conf/global/settings/cloudconfigs/, including names such as dmscene7, dmscene72, and dmscene73. Identify which nodes appear orphaned or incomplete by checking for a blank icon, missing thumbnail, or stale modification date.

  3. Prepare the details for Adobe Support:

    • The affected environment or environments, such as Production, Development, or Stage.
    • The exact names of the orphaned or incomplete nodes to remove.
    • The name of the active configuration node to preserve.

  4. Submit a request to Adobe Support asking for backend removal of the identified orphaned or incomplete Dynamic Media configuration nodes. Note: In AEM as a Cloud Service production, CRXDE is read-only and the AEM interface doesn’t provide this deletion. Don’t attempt to delete the configuration nodes directly.

  5. After Adobe confirms the removal:

    • Check in the AEM interface that the intended active Dynamic Media configuration remains.
    • Test Dynamic Media synchronization and publishing.
recommendation-more-help
experience-cloud-kcs-help-kbarticles