Bulk Reference Processor returns zero results after removing custom index in Adobe Experience Manager
This article explains how to resolve an issue where the Bulk Reference Processor utility in Adobe Experience Manager (AEM) returns zero results after removing a custom SlingOrderedFolder index, and provides steps to validate index removal and troubleshoot further.
Description description
After removing a custom index such as SlingOrderedFolder-custom-2 from your AEM repository, you find that the Bulk Reference Processor utility continues to return zero results. This occurs if the index removal is incomplete or if the repository hasn’t been fully updated to reflect the change.
Environment
- Adobe Experience Manager (all versions)
Symptoms
- Bulk Reference Processor utility returns zero results for asset queries.
- Log files show no eligible assets found for processing, and the tool doesn’t emit the expected queries.
Cause
A custom index (For example: SlingOrderedFolder-custom-2) blocks the Bulk Reference Processor from returning results. Removing the index requires complete removal from both the codebase and the repository, followed by a successful deployment and validation.
Resolution resolution
Follow the steps below to resolve the issue:
-
Remove the custom index definition from your codebase and repository. For guidance, refer to AEM User Guide: Content Search and Indexing.
-
Deploy your changes using the Cloud Manager pipeline to ensure the index removal is applied to your environment.
-
After deployment, use the AEM Index Manager or Oak Index tools to confirm that the custom index is no longer present and that no residual index definitions remain.
-
Enable debug logging for the following loggers to capture queries executed by the Bulk Reference Processor utility:
-
com.day.cq.search -
org.apache.jackrabbit.oak.query -
org.apache.jackrabbit.oak.plugins.index
-
-
Review the logs to verify that queries are being executed as expected when running the Bulk Reference Processor.
-
If the utility still returns zero results and no queries are logged, contact Adobe Support for further assistance.
To verify, run the Bulk Reference Processor utility, and check that eligible assets are now returned as expected.