Dynamic translation does not work properly on a field with more than one languageIssue It happens sometimes that a field contains multiple languages (for instance English and Chinese), and that you try to click on the "translate" button. Even though your preferred language is set to English for example, you may have the message "This content is written in your preferred language. No need to translate." You still have the Chinese part not translated.ResolutionFor a given text, language of the given text will be detected by the external translation service provider and how it determines the language varies from one translation service to another. ServiceNow does not have any role in this part.So, if the translation service detects the language for a given text and that is same as user's preferred language, then this error message is shown.Translation service usually detects one language (which is also equivalent to user's preferred language) even in the case where 2 different languages are used in a single text.ServiceNow does not have control on how the translation service should detect the language of given text and translate the same based on the text content. Some tests have been performed with different translation providers:While hitting MS/IBM/Google translate API directly using an independent REST client, we got the observations:Microsoft: Detects the text as English, hence cannot not translate (when user's preferred language is set to English)IBM: Unable to identify the source language, hence cannot translateGoogle: Should detect the language as the second one present in the text, hence should translate successfully