DocumentationExperience Cloud KCS

AEM as a Cloud Service pipeline deployment fails with INDEXING_FAILED when environment is hibernated

Last update: August 20, 2026

This article describes how to resolve AEM as a Cloud Service pipeline deployment failures caused by the target sandbox environment being in a hibernated state.

Description description

Environment

Adobe Experience Manager as a Cloud Service (AEMaaCS) (all versions)

Symptoms

  • Pipeline deployment to a sandbox Stage environment fails during the deployment phase.
  • Errors such as INDEXING_FAILED, UnknownHostException, or 503 errors appear in the deployment logs.
  • Logs indicate that the Author indexing job can’t reach the internal OakRS service.
  • The issue is typically observed when the target environment is hibernated and not ready to accept deployments.
  • The issue may resolve itself when the environment becomes active.

Cause

The pipeline deployment fails because the target sandbox environment is hibernated, preventing internal services (such as OakRS) from being reachable during the index update phase.

Resolution resolution

Follow the steps below to resolve the issue:

  1. Log in to the Cloud Manager console before triggering a deployment.
  2. Navigate to the target sandbox environment, and confirm it isn’t in a hibernated state.
  3. Ensure both Author and Publish services are running and responsive.
  4. If the environment is hibernated, resume it, and wait until all services indicate readiness.
  5. Confirm that the environment status is Ready in the Cloud Manager UI.
  6. Once the environment is active and healthy, re-trigger the pipeline deployment.
  7. Monitor the deployment to ensure it completes without INDEXING_FAILED or connectivity errors.
recommendation-more-help
experience-cloud-kcs-help-kbarticles