AEM duplicate Launch error

[Shaheena_Sheikh]

Hi,

I see the below error when trying to add the modified master page to XTM Translation job. The translation is for Spanish, and the page already exists in Spanish site. The XTM job shows 2 launch created for the spanish page and the duplicate launch page is having name <pagename>1.

Master page: /content/myproject/master-blueprint/en/music/instruments

Spanish page: /content/myproject/master-blueprint/es/music/instruments

launches:

/content/launches/2025/01/30/launch_copy_of_spanish/content/myproject/master-blueprint/es/music/instruments

/content/launches/2025/01/30/launch_copy_of_spanish/content/myproject/master-blueprint/es/music/instruments1

Log

*INFO* POST /content/projects/xtm_translations/spanish/jcr:content/dashboard/gadgets/translationjob1 HTTP/1.1] com.day.cq.wcm.core.impl.page.PageVersionManager Created new version 1.0 for /content/launches/2025/01/30/launch_copy_of_spanish/content/myproject/master-blueprint/es/music/instruments

*ERROR* POST /content/projects/xtm_translations/spanish/jcr:content/dashboard/gadgets/translationjob1 HTTP/1.1] com.adobe.cq.wcm.translation.impl.TranslationLanguageCopy Error while moving delete path 

{}

javax.jcr.ItemExistsException: /content/launches/2025/01/30/launch_copy_of_spanish/content/myproject/master-blueprint/es/music/temp_delete

at org.apache.jackrabbit.oak.jcr.delegate.SessionDelegate.move(SessionDelegate.java:537)

Any suggestions on the issue?

[konstantyn_diachenko · Accepted solution]

Hi @Shaheena_Sheikh ,

The issue you're facing appears to be related to duplicate launch pages and an ItemExistsException error  when adding a modified master page to an XTM translation job. 

Your Spanish page (/content/myproject/master-blueprint/es/music/instruments) has two launches. The second one (instruments1) suggests a duplicate launch issue. AEM is trying to move/delete temporary content in the launch, but a conflicting item already exists at /content/launches/.../temp_delete. This is likely due to a previous failed or incomplete translation job, leaving behind residual content.

Before retrying the translation job, manually check and clean up any leftover launch page in the Tools -> General -> Launches. Retry translation job.

Best regards,

Kostiantyn Diachenko. 

[AmitVishwakarma]

It seems like the issue arises due to a conflict during the translation process, where the system is trying to create a duplicate launch page (<pagename>1) and there's a move operation on a temporary delete path (temp_delete) that fails due to an existing item. This could be related to how the translation workflow is managing page versions and launch creation in AEM.
Suggested solutions:

1. Clear Temporary Data: The error message points to a temp_delete path that might have an existing item. Try clearing any temporary or orphaned data that could be preventing the move operation.
Check /content/launches/2025/01/30/launch_copy_of_spanish/content/myproject/master-blueprint/es/music/temp_delete and ensure no leftover files or conflicts exist.

2. Check for Duplicate Launch Pages: Ensure that no duplicate launch pages are created in the system. It looks like a duplicate launch page (<pagename>1) is being generated due to an existing page. Manually delete or resolve the conflict between the two launch pages (/content/myproject/master-blueprint/es/music/instruments and /content/myproject/master-blueprint/es/music/instruments1).

3. Translation Job Settings: Investigate the XTM job setup. Ensure that it’s correctly configured to avoid creating duplicate launches for the same page and to properly handle versions and page renaming.

4. Version Handling: Review the versioning settings for your pages in AEM. The error may also be related to AEM's versioning system during translation, causing conflicts when handling the existing Spanish page version and the new one. Try creating a new version of the Spanish page and then reattempt the translation.

5. Delete and Recreate Launch: In case the launch data has become corrupted, try deleting the conflicting launch and recreate it with a fresh setup, making sure there are no conflicts in the paths.