AEM Cloud Manager deploy step fails with transient dispatcher error
This article explains how to resolve a scenario where an Adobe Experience Manager (AEM) Cloud Manager pipeline fails during the deploy step due to a transient dispatcher layer error that isn’t related to vanity URL configuration files.
Description description
Environment
Adobe Experience Manager (AEM) Cloud Manager
Issue/Symptoms
AEM Cloud Manager pipelines sometimes fail during the deploy step, even if all previous steps such as validate, build, code quality, and build image complete successfully. In this scenario, the failure occurs in the dispatcher layer, which handles applying and validating HTTP/dispatcher configuration. The error is generic and doesn’t indicate issues with vanity URL configuration files. After the failure, the environment’s services (Author, Publish, Preview) may still be running, suggesting that the issue is transient and resolved automatically on the next startup attempt.
Resolution resolution
Follow the steps below to resolve the issue:
-
Verify that the environment’s services (Author, Publish, Preview) are running after the failed deploy step in Cloud Manager.
-
Re-run the pipeline by triggering the deployment again from Cloud Manager.
-
If the pipeline succeeds on the next run, no further action is required.
-
If the deploy step fails again with a similar dispatcher layer error:
- Investigate the dispatcher and HTTP configuration files for errors or misconfigurations.
- Review deployment scripts and configuration files related to the dispatcher layer for potential issues.
- Ensure that all required vanity URL configuration files are present and correctly configured, even though this wasn’t the cause in this scenario.
-
After making any corrections, re-run the pipeline to verify successful deployment.