DocumentationExperience Cloud KCS

AEM as a Cloud Service: Pipeline deployment delay due to missing vanity URL map file

Last update: September 10, 2026

This article explains how to resolve deployment delays in Adobe Experience Manager (AEM) as a Cloud Service pipelines when dispatcher startup is blocked by a missing vanity URL map file configured in managed rewrite maps.

Description description

Environment

  • Adobe Experience Manager (AEM) as a Cloud Service
  • Pipeline deployment to the Preview publish tier

Issue/Symptoms

  • Pipeline deployment hangs or fails during the dispatcher startup step.
  • Dispatcher logs show repeated attempts to download a managed rewrite map file from a DAM path such as /content/dam/<org>/vanity-maps/<vanity-map-file>.txt, resulting in HTTP 404 responses.
  • The dispatcher configuration, for example in opt-in/managed-rewrite-maps.yaml, contains a rewrite map entry with wait: true, causing dispatcher startup to block until the file becomes available.

Cause

The dispatcher is configured to wait for a vanity URL map file that is not yet available in the DAM. When the file is missing and wait: true is configured, dispatcher startup is blocked, resulting in deployment delays or failures.

Resolution resolution

Follow the steps below to resolve the issue.

  1. Determine whether the vanity URL map file must be available at dispatcher startup.

    • If the redirects are not required immediately, continue to step 2.
    • If the redirects must be available at startup, continue to step 4.

  2. To avoid blocking dispatcher startup, modify the dispatcher configuration.

    • In the opt-in/managed-rewrite-maps.yaml file, set wait: false for the affected map entry.
    code language-none 
    source: /content/dam/<org>/vanity-maps/<vanity-map-file>.txt
target: /etc/httpd/conf.d/rewrites/<vanity-map-file>.map
wait: false

  3. Redeploy the pipeline.

  4. If the vanity URL map file is required at startup, ensure that the DAM asset (for example, /content/dam/<org>/vanity-maps/<vanity-map-file>.txt) is published and accessible on both the Publish and Preview tiers in the target environment.

  5. Verify that accessing the file on the Preview instance returns a successful HTTP 200 or 302 response.

  6. Rerun the pipeline deployment.

  7. Confirm that the pipeline deployment completes successfully and that dispatcher starts as expected.

Pipeline-Free URL Redirects

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