DocumentationExperience Cloud KCS

Incomplete query results on Publish after Content Transfer Tool migration in AEM as a Cloud Service

Last update: October 26, 2026

Adobe Experience Manager as a Cloud (AEMaaCS) Service may return incomplete query results on the Publish tier after a Content Transfer Tool migration when the OOTB damAssetLucene index is selected instead of the intended custom index and isn’t reindexed correctly. To resolve the issue, identify the index used by the affected queries, reindex damAssetLucene when applicable, and verify that Publish and Author return consistent results.

Description description

Environment

  • Adobe Experience Manager as a Cloud Service (AEMaaCS)
  • Content Transfer Tool migration
  • Publish tier

Issue/Symptoms

  • After migrating content with the Content Transfer Tool, queries on the Publish tier return fewer results than expected even though the content exists in the repository.
  • Custom Oak Lucene indexes deployed through Cloud Manager may be affected.
  • Site-wide search pages may display significantly fewer items than expected, while direct repository reads confirm that the missing content exists.
  • Queries on the Author tier return the expected results, but the same queries on the Publish tier don’t.
  • Investigation may show that queries use the OOTB damAssetLucene index instead of the intended custom index and that the OOTB index wasn’t reindexed correctly after migration.

Resolution resolution

Follow the steps below to resolve the issue:

  1. Identify which Oak Lucene index resolves the affected queries on the Publish tier. Use the Query Performance tool or query debugger to determine whether the OOTB damAssetLucene index is used instead of the custom index.
  2. If the OOTB damAssetLucene index is used, trigger a full reindex of the index on the affected Publish environment. Update the reindex property to true on the index definition node in the repository or use the JMX console.
  3. Monitor the reindexing process until it completes.
  4. After reindexing, rerun the affected queries and verify that the expected content is returned on the Publish tier. Compare the results with the Author tier to ensure consistency.
  5. Be aware that the issue may recur after future Content Transfer Tool migrations and may require reindexing again.
recommendation-more-help
experience-cloud-kcs-help-kbarticles