DocumentationExperience Cloud KCS

Pipeline execution failures during indexing in AEM as a Cloud Service

Last update: September 4, 2026

This article explains how to troubleshoot pipeline execution failures in AEM as a Cloud Service that occur because of indexing errors during deployment. To fix this, review the indexing step and pipeline logs, identify the affected index, update the index definition when a version conflict exists, and collect the required information for Adobe Support when corruption or another unrecoverable error persists.

Description description

Environment

  • Adobe Experience Manager as a Cloud Service
  • Cloud Manager deployment pipeline
  • Development, Production, and other target environments

Issue/Symptoms

Pipeline executions in AEM as a Cloud Service fail or become stuck during deployment because of issues with Lucene/Oak indexes.

  • The pipeline doesn’t progress beyond the indexing step.
  • Error messages reference indexing failure, index corruption, or version conflicts.
  • Logs include messages such as indexing failure, CorruptIndexException, codec header mismatch, or Invalid seek request.

Cause

The relevant causes include issues with custom index definitions, index corruption, and version mismatches between custom indexes.

Resolution resolution

Follow the steps below to resolve the issue:

  1. Review the pipeline execution in Cloud Manager and determine whether the failure occurred during the indexing step.
  2. Review the pipeline logs for details. Look for messages such as indexing failure, CorruptIndexException, codec header mismatch, or Invalid seek request.
  3. Identify the specific index referenced in the error message, if available. The path can appear as /oak:index/your-custom-index.
  4. If the error indicates a version conflict, such as an attempt to add a custom index with a lower version number than an existing index, update the codebase to merge the changes into the latest index version and increment the version number appropriately.
  5. If the error indicates index corruption or another unrecoverable error, collect the relevant log excerpts and record the affected index paths.
  6. After making the necessary changes to the index definitions, retry the pipeline execution.
  7. If the pipeline remains stuck or the error persists, provide the collected log details and affected index information when you contact Adobe Support.
  8. After the issue is remediated, rerun the pipeline to confirm that the deployment succeeds.

Notes:

  • In AEM as a Cloud Service, manage index changes in the project codebase and deploy them through Cloud Manager. Don’t manually modify runtime index nodes.
  • Remove customer-specific paths, hostnames, environment identifiers, and other sensitive information from log excerpts before sharing them with Adobe Support.
recommendation-more-help
experience-cloud-kcs-help-kbarticles