AEM Assets: Resolving Content Fragment publish status inconsistencies after content copy
This article explains how to address inconsistent Content Fragment publish statuses in Adobe Experience Manager (AEM) Assets after using Content Copy or package import to transfer content between Author environments.
Description description
When Content Fragments are transferred between AEM Author environments using the Copy content interface or package import, the publish status of the content in the destination environment doesn’t match the status in the source environment. This can result in Content Fragments appearing as published or unpublished in the AEM editor, but showing a different status when accessed via API or GraphQL. This discrepancy can block business operations that rely on synchronized content status across environments. No specific error messages are logged during the operation, and logs don’t always be available for review.
Environment
- Adobe Experience Manager (AEM) Assets (all versions)
Symptoms
- Content Fragments show different publish statuses in the AEM editor versus API or GraphQL responses after content copy or package import.
- Inconsistent status reporting between the AEM UI and API endpoints.
- Business processes are impacted due to unsynchronized content status.
Cause
The current design of the Content Copy and package import processes in AEM doesn’t preserve the publish state or version history of Content Fragments when transferring content between Author environments. As a result, publish status must be re-established in the Destination environment after content transfer.
Resolution resolution
Follow the steps below to resolve the issue:
-
Log in to the destination AEM Author environment where the Content Fragments were imported.
-
Bulk republish the affected Content Fragments:
-
Use the tree activation feature or an automation script to republish all transferred Content Fragments from the destination author environment.
-
For large content sets, avoid manual, fragment-by-fragment republishing; use bulk operations where possible.
-
-
Verify that the publish status is now consistent:
- Check that the status in the AEM editor matches the status returned by the API or GraphQL endpoints.