DocumentationExperience Cloud KCS

AEM Cloud Service RDE stuck in deployment after installing large content packages

Last update: October 12, 2026

In Adobe Experience Manager Cloud Service, a Rapid Development Environment becomes unresponsive and remains in a Deployment in progress state after installing a large or deeply nested content package. CLI commands also return internal errors or show that the environment is unavailable. To fix this issue, address the resource exhaustion caused by the large or deeply nested content structure.

Description description

Environment

Adobe Experience Manager (AEM) Cloud Service Rapid Development Environment (RDE), all versions.

Symptoms

  • The RDE remains in “Deployment in progress” for an extended period after installing a large content package via Package Manager.
  • Attempts to restart or check the status of the RDE using CLI commands (such as aio aem rde restart or aio aem rde status) fail with internal errors or indicate that the environment is unavailable.
  • The environment is unresponsive and does not process requests.

Cause

Excessive resource consumption during the rendering of deeply nested or very large content structures. This can lead to repeated resource exhaustion errors, such as TooManyCallsException and OutOfMemoryError, which in turn cause repository connection loss, instance shutdown, and failed recovery, leaving the RDE stuck in deployment.

Resolution resolution

  1. Before deploying content packages to your RDE, review and limit the size and depth of content structures. Avoid creating test pages or components with excessive nesting or very large numbers of child nodes, as these can exhaust system resources during rendering.

  2. If your RDE becomes unresponsive after installing a large or deeply nested content package:

    1. Attempt to restart the RDE using the CLI command: aio aem rde restart
    2. After the restart, check the environment status with: aio aem rde status

  3. If the environment remains unresponsive and standard restart commands don’t recover the RDE, consider the following:

    1. Collect the error output from your CLI commands and review it for any actionable errors.
    2. As a last resort, perform an RDE reset. Note: Resetting the RDE removes all existing project code and content from the instance. Proceed with a reset only if you’re prepared to lose all current data in the environment.

  4. After recovery, reintroduce content in smaller, incremental sets and avoid deploying large or deeply nested content structures to prevent recurrence.

  5. Once the RDE is responsive, confirm that you can access the environment and perform standard operations, such as viewing pages and using Package Manager.

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