DocumentationExperience Cloud KCS

Resolve AEM as a Cloud Service deployment failures at Update Indexes step

Last update: September 8, 2026

If your AEM as a Cloud Service pipeline deployment fails at the Update Indexes step, this is usually caused by a custom index with a version higher than the corresponding base product index, or a missing required type property. Review your custom index definitions, correct the productVersion and type properties, and redeploy to resolve the failure.

Description description

Environment

Adobe Experience Manager as a Cloud Service (all environments)

Symptoms

  • Pipeline deployments fail at the Update Indexes step.

  • Error logs may include messages such as:

    • Cannot add a new customized index … because the product version for this index is higher than the product index of the existing latest index.
    • No type property found for index at path …
    • Ignoring index … without a type

  • In some cases, errors related to repository initialization (RepoInit) scripts may appear, such as attempts to set ACLs on non-existent paths.

  • Deployments to any environment (for example, development, staging, and production) are blocked, preventing releases.

Cause

  • The custom index definition specifies a product version that is higher than the base product index version present in the environment.
  • The custom index definition is missing the required type property.
  • RepoInit scripts attempt to set ACLs on repository paths that do not exist.

Resolution resolution

Follow the steps to resolve the issue.

  1. Review your custom index definitions (for example, /oak:index/yourCustomIndexName) in your codebase.

  2. Check the productVersionproperty of each custom index:

    • Ensure its productVersion does not exceed the product index version of the corresponding base index (for example, /oak:index/cqPageLucene or /oak:index/damAssetLucene).
    • If the custom index version is higher, update it to match or be compatible with the base product index version.

  3. Ensure each custom index includes the mandatory type property (for example, type: lucene), adding or correcting it if missing.

  4. If you encounter RepoInit ACL errors, review your RepoInit scripts for any ACL assignments to repository paths:

    • Ensure that the target paths exist before setting ACLs, or modify the script to create the required paths as part of the deployment.

  5. After making the necessary corrections, trigger the pipeline again via Adobe Cloud Manager.

  6. Monitor the Update Indexes step to verify that the deployment completes successfully.

recommendation-more-help
experience-cloud-kcs-help-kbarticles