DocumentationExperience Cloud KCS

Scheduled Launches in AEM Cloud do not publish due to nested Launch structure

Last update: October 6, 2026

In Adobe Experience Manager as a Cloud Service Cloud (AEMaaCS), Scheduled Launches do not publish at the configured time when Launches are created from other Launches. The issue occurs in a nested Launch structure, where scheduled promotion updates the parent Launch instead of the live source page. To resolve the issue, create Launches directly from the live source.

Description description

Environment

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

Issue/Symptoms

  • Scheduled Launches do not publish at the configured time.
  • The source page and published content are not updated after the scheduled go-live.
  • Manual intervention is required to update and publish the content.
  • The issue is observed when Launches are created from other Launches, resulting in a nested Launch structure.
  • Manual promotion and publication of Launches created directly from the live source page work as expected.

Root cause

When a Launch is created from another Launch (nested structure), scheduled promotion updates the parent Launch instead of the live source page. This prevents the scheduled changes from being applied to the intended live content.

Resolution resolution

Follow the steps below to resolve the issue:

  1. When creating a new Launch, always select the live source page as the source. Avoid creating a Launch from an existing Launch.

  2. Make the required content changes within the new Launch.

  3. Mark the Launch as Production Ready and select Promote Full Launch.

  4. Promote the Launch back to the live source page.

  5. Publish or activate the source page after promotion to ensure the changes are reflected live.

  6. For existing nested Launches:

    1. Identify any Launches that were created from other Launches.
    2. Copy any pending changes from these nested Launches into a new Launch created directly from the live source page.
    3. Remove or archive the old nested Launches after preserving required content.

  7. Test scheduled promotions using the new flat Launch structure to confirm the issue is resolved.

  8. If the issue recurs, collect Author logs from 30 minutes before to 60 minutes after the scheduled promotion for further analysis.

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