DocumentationExperience Cloud KCS

Custom workflows and metadata schemas not updating after Cloud Manager deployment

Last update: July 23, 2026

This article explains how to address situations where custom workflow models and metadata schemas do not update as expected after deploying content packages using Cloud Manager in Adobe Experience Manager (AEM) Assets.

Description description

Environment

Adobe Experience Manager (AEM) Assets (all versions)

Issue/Symptoms

  • After deploying a content package (such as a ui.content package) via Cloud Manager, custom workflow models and metadata schemas are not updated to the latest version in the environment.
  • The issue occurs consistently with each deployment.
  • Changes to custom workflows are not reflected after deployment.
  • Updates to custom metadata schemas are missing post-deployment.
  • No explicit error messages are shown during deployment, but the expected configuration changes are not present.

Cause

This issue is typically caused by one of the following:

  • The mutable ui.content package is not reinstalled during Cloud Manager deployments, preventing new changes from being applied.
  • Workflow models and metadata schemas are not synchronized correctly between configuration paths after deployment.

Resolution resolution

To fix the issue, follow these steps:

  1. Log in to your AEM environment after deployment.
  2. Navigate to Package Manager at /crx/packmgr/index.jsp.
  3. Confirm that the latest ui.content package is installed and matches the expected version.
  4. If the package is not updated, increment the package version and redeploy using Cloud Manager to ensure the new package is picked up.
  5. Open the package and verify that all required configuration paths (such as /conf, /apps, /var/workflow/models, and any custom schema paths) are included.
  6. Ensure that workflow models and metadata schemas are present in the correct locations within the package.
  7. After deployment, navigate to Tools > Workflow > Models in AEM.
  8. Confirm that the custom workflow models are synchronized and reflect the latest changes. If necessary, synchronize or re-import the workflow models.
  9. Review Cloud Manager deployment logs for any warnings or errors related to package installation or configuration synchronization.
  10. If the issue persists after completing these steps, gather relevant logs and package details before contacting Adobe Support.
recommendation-more-help
experience-cloud-kcs-help-kbarticles