Missing content fragments in Adobe Experience Manager Sites as a Cloud Service
This article explains how to troubleshoot a content fragment that is missing from its expected repository path in Adobe Experience Manager (AEM) Sites as a Cloud Service. The content fragment might not appear in the Content Fragments console or be available for editing or publishing. A missing content fragment can affect workflows that depend on its presence, such as publishing updates to a live site or synchronizing content across environments. To fix this, check the expected repository paths, review recent changes and version history, and verify the publication status.
Description description
Environment
- Adobe Experience Manager as a Cloud Service (all versions)
- Content Fragments managed through the Content Fragments or Assets console
Symptoms
- A specific content fragment is missing from its expected repository path, such as
/content/dam/<your-site>/<your-folder>/<fragment-name>. - The content fragment is live on an external site but isn’t visible in AEM Assets.
- A draft version of the content fragment exists, but the published version isn’t accessible.
- Other content fragments in similar paths are visible and accessible.
Cause
Common causes include repository synchronization issues, accidental deletion, or visibility problems in the AEM Assets user interface. Recent changes or deployments also affect the availability of specific content fragments.
Resolution resolution
Follow the steps below to resolve the issue:
- Log in to the Assets console.
- Navigate to the expected repository path where the content fragment should reside, such as
/content/dam///. - Check all relevant repository paths for the content fragment.
- Review recent deployments, migrations, or other changes that could have affected the visibility or existence of the content fragment.
- Review the version history or audit logs, if available, to identify accidental deletions or modifications.
- If a draft version of the content fragment exists, verify whether it was published.
- Verify that the correct version is published and available in the intended environment.
- Attempt to create a new content fragment with the same name and in the same path to determine whether errors or restrictions prevent creation.
- If creation succeeds, verify that the new content fragment is visible and accessible.
- Confirm that the missing content fragment is visible in the Assets console and accessible for editing or publishing.
Note: Confirm with the appropriate administrator or SME before creating a new content fragment with the same name and path, because this action changes repository content.