Custom index reindexing issues in AEM as a Cloud Service - Sites

Last update: March 3, 2025

Custom indexes don’t reindex properly in the development environment of AEM when  async and  async-previous properties in the index configuration are incorrect. Implementing Tika configuration and correcting async properties can resolve this issue.

Description

Environment

Adobe Experience Manager as a Cloud Service (AEMaaCS) - Sites (Development environment)

Issue

When custom indexes fail to reindex properly, SQL2 queries on both the author and publish instances do not return the expected results. This issue particularly impacts search indexes for Content Fragments, leading to the following problems:

  • Queries using custom indexes return zero results despite the presence of known Content Fragments.
  • Suboptimal indexing performance due to indiscriminate data indexing, which can slow down query execution.

Cause

  • The async  and async-previous  properties in the index configuration are incorrect. This misconfiguration leads to a failure in the indexing process.
  • Indexing is slow even though the repository is small. There are several custom indexes that index all the data, causing extensive text extraction.

Resolution

  1. To improve indexing performance, implement Tika configuration similar to the out-of-the-box damAssetLucene indices. Refer to Content Search and Indexing in the AEM as a Cloud Service guide for detailed instructions.
  2. Verify and correct any incorrect values found in the async  and async-previous  index properties.
recommendation-more-help