AEM Assets translation from en US to es US fails in Adobe Experience Manager

This article addresses translation failures when attempting to translate from en_US to es_US in Adobe Experience Manager Assets using AI Translation Integration.

Description description

Environment

Adobe Experience Manager (AEM) Assets (all versions)

Issue/Symptoms

  • When attempting to translate content from en_US (English - United States) to es_US (Spanish - United States) using the AEM AI Translation Integration (with Azure OpenAI as the backend), the following error appears at the start of the translation process: The Translation Provider doesn’t support translation for the selected language pair.
  • Translation from en_US to es_ES (Spanish - Spain) works as expected.
  • The error occurs during translation execution, not during project creation.
  • The translation provider is configured via AEM AI Translation Integration, not the classic Microsoft Translator connector.
  • Internal locale references list es_ES but do not list es_US.
  • The issue is reproducible by creating a translation project and sending it for translation with the en_US → es_US pair.
  • Translation project UI example.

Resolution resolution

Follow these steps to resolve the issue:

  1. Confirm which translation provider is used in the translation project or cloud configuration, such as Azure OpenAI, SDL/WorldServer, Smartling, GlobalLink, or a custom connector.
  2. Check the provider documentation to verify supported Spanish target locales, such as es, es-ES, es-LA, es-MX, or es_US.
  3. Test translation using supported locales such as es, es-ES, or es-MX.
  4. If the UI allows it, test both es_US and es-US as target locales.
  5. Review the supported languages list in the AEM GenAI or DXTA configuration.
  6. Verify that es_US or an equivalent locale mapping is present.
  7. If es_US is missing, add or map the locale according to the provider documentation.
  8. Capture the exact runtime error or HTTP response returned by the translation provider if the error persists.
  9. Determine whether the rejection comes from AEM validation or the translation provider.
  10. If the provider does not support es_US, review the provider documentation or contact the provider’s support team.
  11. Use a supported Spanish locale for U.S. Spanish content if required.
recommendation-more-help
experience-cloud-kcs-help-kbarticles