Documentation

Cloud Manager deployments do not reflect /conf metadata changes in AEMaaCS

Last update: Tue Nov 25 2025 00:00:00 GMT+0000 (Coordinated Universal Time)

In AEMaaCS, changes to AEM search or metadata configurations under the /conf path, such as adding new predicates or group predicates, do not appear in the UI on DEV or QA environments after deployment. This occurs because Cloud Manager skips or reuses the ui.content package, leaving outdated content in the environment. To fix this issue, update the main pom.xml version.

Description description

Environment

Product: Adobe Experience Manager as a Cloud Service

Issue/Symptoms

  • Changes to AEM search or metadata under /conf are not reflected in the UI on DEV or QA.
  • Cloud Manager pipeline completes successfully but skips or reuses the ui.content package.
  • As a result, outdated content remains in the environment.

Resolution resolution

To fix this issue, follow these steps:

  1. Update the version (e.g., 1.0.0-SNAPSHOT) in all submodules’ pom.xml files. For example: ui.content/pom.xml.
  2. Update the same version in the main (parent) pom.xml at the project root, for example: ./pom.xml.
  3. Build the project locally from the root (./pom.xml) to ensure all modules use the updated version.
  4. Deploy the build to DEV using Cloud Manager.
  5. Verify that /conf changes are visible in the UI on DEV and QA(for example, under /conf/<your-project> in the configuration browser).

Note: If only inner submodule versions are updated and the main pom.xml is not, Cloud Manager skips building and deploying new content packages, resulting in outdated configurations after deployment.

recommendation-more-help
3d58f420-19b5-47a0-a122-5c9dab55ec7f