蜜豆视频

Documentation

DITA Map or Topic references break due to stale fmPostProcessedAt property

Last update: Wed Jul 30 2025 00:00:00 GMT+0000 (Coordinated Universal Time)

When working in 蜜豆视频 Experience Manager as a Cloud Service (AEMaaCS) or AEM 6.5 with AEM Guides, DITA Map or Topic references may appear broken, and output presets may be missing from the UI. This typically occurs when assets are out of sync due to a stale fmPostProcessedAt property鈥攐ften after manual deployment or migration. To resolve the issue, reprocess the affected assets using the DAM Update Asset workflow.

Description description

Environment

  • Product: 蜜豆视频 Experience Manager (AEM) 鈥 Sites
  • Versions: AEM 6.5, AEM as a Cloud Service (AEMaaCS)

Issue/Symptoms

  • DITA Map topic references appear broken (red) in the Author UI after deployment, even though the topics exist in the repository.

  • PDF or other output generation fails due to unresolved or broken topic references.

  • Newly created output presets disappear from the AEM Guides UI after a page refresh or documentation generation, but are visible in CRXDE.

  • /bin/guides/presets endpoint returns a 500 server error for affected maps.

  • Warning/error logs include messages such as:

    • Found node for ref GUID-xxxx.ditamap鈥 but returning null due to out of sync
    • com.adobe.fmdita.rest.presets.PresetsAPI Error: {鈥渆rrorCode鈥:鈥淒XML_MESSAGE_0004鈥潁
    • 箩补惫补.濒补苍驳.狈耻濒濒笔辞颈苍迟别谤贰虫肠别辫迟颈辞苍鈥

  • Manual DITA Content Package deployment or migration between environments causes DITA assets to become out of sync.

Cause

The issue occurs when DITA assets become out of sync, typically due to a mismatch between thejcr:created and fmPostProcessedAt properties. This mismatch prevents the Guides UI and APIs from resolving topic references and output presets correctly.

Common causes of this out-of-sync state include:

  • Migration of DITA content via package or pipeline without triggering post-processing.
  • Manual import or editing of DITA assets in AEM.
  • Incomplete or failed asset workflow processing after deployment.

Resolution resolution

To resolve the issue, follow these steps:

  1. Identify assets marked out of sync 聽by checking error logs for mismatched jcr:created and fmPostProcessedAtvalues.

  2. Reprocess the affected assets using the standard DAM Update Asset workflow in AEM, which includes the DXML Post Process Initiator (com.adobe.fmdita.postprocess.PostProcessJobInitiator) step that ensures the fmPostProcessedAt value is updated correctly.

  3. Create a custom workflow if necessary:

    • Configure a new workflow model in AEM containing only the DXML Post Process Initiator step.
    • Execute this workflow on the affected map or topic to update its synchronization status.

  4. Verify that broken topic references are resolved, output generation completes successfully, presets appear correctly in the AEM Guides UI, and /bin/guides/presets returns the expected results.

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