Update language copy launches are not promoted automatically

Explore the steps to manually promote language copy launches in AEM as a Cloud Service (AEMaaCS) - Sites, addressing the issue where automatic promotion does not occur despite configuration settings.

Description description

Environment

Adobe Experience Manager as a Cloud Service (AEMaaCS)

Issue/Symptom(s)

During the Update Language Copy process in AEM as a Cloud Service - Sites, launches are created but not promoted automatically. This is despite the translation project being configured for automatic promotion.

Steps to Reproduce:
The issue has been reproduced using the out-of-the-box (OOTB) AEM guides WKND project with the following steps:

  1. Create a new page story_time under sites/wknd/language-masters/en.
  2. Create a new translation project selecting the target language - French. Ensure that under Advanced, the new project has Automatically Promote Translation Launches  checked.
  3. Add the story_time page to the translation job and create a language copy.
  4. Verify that a new page story_time has been created under sites/wknd/language-masters/fr.
  5. Make a change to the source page en/story_time.
  6. Add a new translation job to the already created project and add the same source page en/story_time and select Update language copy.
  7. Since the project has Automatically Promote Translation Launches  checked it is expected that the language copy will be updated with the new content, however, the fr/story_time page doesn’t have the updates.
  8. Select en/story_time and go to References  >   Language copies.
  9. Select the French language copy and select update language copies.
  10. Again, the language copy is not updated with the new content.
  11. The language copy will only be updated if we manually promote the launch from the language copy’s references.

Resolution resolution

The experienced behavior is as designed.

We only promote launches after the content of the translation job is completed. Therefore, to promote a launch, you need to start a translation job following the language copy workflow update.

You can, however, manually promote the launch from the language copy’s references (as described in step 11), as launch functionality is independent of the translation process.

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