Documentation

Redirect properties don’t roll out to AEM live copies

Last update: Thu Feb 05 2026 00:00:00 GMT+0000 (Coordinated Universal Time)

Redirect settings configured in the Redirect and Permanent Redirect fields on blueprint pages don’t propagate to live copies during rollout because the default MSM action excludes redirect-related properties. To resolve the issue, override the default OSGi configuration to include these properties.

Description description

Environment

  • Product: Adobe Experience Manager as a Cloud Service (AEMaaCS) – Sites
  • Scenario: Multi-Site Manager (MSM) with live copy rollouts

Issue/Symptoms

  • The redirects set in the Redirect or Permanent Redirect fields doesn’t appear on live copies after rollout.
  • cq:redirectTarget remains missing on live copies post-rollout.
  • cq:redirectPermanent/redirectStatus doesn’t propagate from blueprint to live copies.
  • Live copies serve original pages instead of configured redirect targets.

Resolution resolution

Follow these steps to address the issue:

  1. Redefine cq.wcm.msm.action.excludedprops and add redirectTarget|redirectStatus to the regex: (designPath|template|lastTranslationUpdate|targetEngine|robotsTags)$).* like this cq:(?!(designPath|template|lastTranslationUpdate|targetEngine|robotsTags|redirectTarget|redirectStatus)$).*
  2. Merge changes carefully with existing out-of-the-box configurations to avoid impacting other live copies.
  3. Deploy and test this configuration change thoroughly in a lower environment.
  4. After verification, apply the configuration change to Stage or Production environments as appropriate.
  5. Validate that redirect properties propagate correctly during rollout by checking the relevant fields on live copies.

Configuring OSGi for Adobe Experience Manager as a Cloud Service in the AEM as a Cloud Service User Guide

recommendation-more-help
3d58f420-19b5-47a0-a122-5c9dab55ec7f