The Translation Provider Does Not Receive Content in New or Custom Languages

The Connector successfully sends content for translation in new or custom languages but it does not reach the translation provider.

Possible Issue Explanation Solution
The Content API Platform does not have the updated language mapping. Your company and your translation provider may use different language codes in their technology/workflows. The Content API Platform can map language codes in Adobe Experience Manager to those expected by the translation provider. Contact Lionbridge Connector Support to request a review of the Connector language mapping for the translation provider to ensure that the new language is correctly mapped for the target platform. For details, see How to Contact Lionbridge Connector Support.
The translation provider requires that source-target languages pairs are configured before any new translation requests. The translation platforms of most translation provider require that source-target language pairs are configured. Contact the translation provider and verify that the all source-target language pairs are configured.