DocumentationExperience Cloud KCS

Custom index deployment fails during SIM migration in AEM as a Cloud Service

Last update: August 28, 2026

This article explains how to resolve deployment failures in Adobe Experience Manager as a Cloud Service that occur when custom indexes become stuck in a temp-async state during migration to Simplified Index Management (SIM). The recommended solution involves resetting the environment and reintroducing custom indexes incrementally.

Description description

Environment

  • Adobe Experience Manager as a Cloud Service
  • Simplified Index Management (SIM)

Symptoms

  • Deployment pipelines fail during migration to SIM.
  • Custom indexes are stuck in a ‘migration in progress’ state.
  • Index properties include async = temp-async,nrt and async-previous = async,nrt.
  • Log messages include errors such as Failure when applying the indexing data and No current checkpoint found for lane [ async,nrt].

Cause

This issue occurs when multiple custom indexes are migrated simultaneously, causing the indexing job to leave indexes in an inconsistent state that cannot be resolved automatically.

Resolution resolution

Follow these steps to resolve the issue.

  1. Temporarily remove the affected custom indexes from your SIM configuration, or comment out their entries in your index diff file.

  2. On AEM Author environments with CRXDE access, such as Development or local environments, delete the affected index nodes under /oak:index for each problematic custom index.

  3. For the Publish and Preview environments in AEM as a Cloud Service, where direct CRXDE access is unavailable, reset the environment using Cloud Manager. Note: This action starts Author, Publish, and Preview with a clean repository.

  4. Run a Cloud Manager pipeline that does not include any custom indexes. Confirm that the indexing step completes successfully without errors.

  5. Reintroduce the custom indexes incrementally through SIM:

    • Add one custom index at a time.
    • Run the Cloud Manager pipeline after each addition.

  6. After each deployment, verify the index configuration on Author:

    • Confirm that the index has async = [ "async","nrt" ].
    • Confirm that the index does not contain an async-previous property.
    • Confirm that only one active version of each custom index exists in the codebase.
    • Confirm that the index is not left in a temp-async state.

  7. Confirm that the Cloud Manager pipeline completes successfully and that the affected functionality works as expected.

Notes:

  • Index configuration changes for AEM as a Cloud Service must be managed in the project codebase and deployed through Cloud Manager.
  • When troubleshooting several custom indexes, reintroduce them one at a time to identify the index associated with the deployment failure.
  • If the deployment continues to fail after the indexes have been isolated and reintroduced incrementally, contact Adobe Support through the standard support process.
recommendation-more-help
experience-cloud-kcs-help-kbarticles