DocumentationExperience Cloud KCS

AEM Guides: Translation projects for sr-LA not created due to unsupported language code

Last update: August 18, 2026

Translation projects for the Serbian locale sr-LA don’t appear in Adobe Experience Manager (AEM) Guides, and translation job creation fails with unsupported language errors. AEM doesn’t include sr-LA as a supported language code in the language registry, so the translation workflow doesn’t create the corresponding translation project. Add a custom language definition for sr-LA in the AEM language registry and recreate the translation job. To resolve the issue, add and validate a custom sr-LA language definition.

Description description

Environment

Adobe Experience Manager (AEM) Guides (all versions)

Issue/Symptoms

  • Topics display as In Progress for the Serbian locale sr-LA, but no corresponding translation project appears in AEM.
  • Attempts to create translation jobs forsr-LA fail.
  • The UI displays an inconsistent translation overview.
  • Logs display the following errors:
Caused by: com.day.cq.workflow.WorkflowException: Translation for destination language is not supported
    at com.adobe.cq.wcm.translation.impl.process.TranslateSitePrepareProcess.execute(TranslateSitePrepareProcess.java:228)
...
Error while translating language copy for .../sr-LA in null.

The AEM language registry (/libs/wcm/core/resources/languages) does not include sr-la or sr_LA as a supported language code. Only the following Serbian variants are defined:

  • “sr”: { “language”: “Serbian”, “defaultCountry”: “sr_rs”, “country”: “*” }
  • “sr_rs”:
  • “sr_ba”:
  • “sr_me”:

Reproduction Conditions

  • Attempt to create or view translation projects for sr-LA in AEM Guides.
  • a { text-decoration: none; color: rgba(70, 79, 235, 1) } tr th, tr td { border: 1px solid rgba(230, 230, 230, 1) } tr th { background-color: rgba(245, 245, 245, 1) }
    Usesr-LA as the target locale.
  • The issue is reproducible on clean out-of-the-box AEM instances and across multiple environments.

Cause

The root cause is that sr-LA is not a default language code supported by AEM’s language registry. The translation workflow rejects unsupported language codes, preventing translation project creation for sr-LA.

Resolution resolution

Follow these steps to resolve the issue:

  1. Check the language registry at /libs/wcm/core/resources/languages to confirm that sr-la or sr_LA is not present.

  2. Create an overlay at /apps/wcm/core/resources/languages.

  3. Add a custom language node:

    • /apps/wcm/core/resources/languages/sr-la
    • language = "Serbian"
    • country = "Latin"

  4. Create a translation project for sr-LA in AEM Guides after adding the custom language node.

  5. Confirm that the translation job has been created and that the workflow proceeds as expected.

  6. If translation projects for sr-LA previously worked, verify whether custom language definitions were removed or modified recently.

  7. Restore or update custom language codes as needed.

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