Error messages in Dynamic Translation

  • Release version: Yokohama
  • Updated January 30, 2025
  • 1 minute to read
  • You must be aware of a few error scenarios while using Dynamic Translation.

    Error messages on forms and activity streams

    Error messages are displayed when the text cannot be dynamically translated on forms activity streams.
    Table 1. Forms and activity streams
    Scenario Error message
    Field has no value.
    Note:
    This scenario is applicable only for fields on the form.
    No text to translate.
    Text to be translated is already in the logged-in user's preferred language. This content is written in your preferred language. No need to translate.
    Text cannot be translated to the user's preferred language by the default translation service provider. Text cannot be translated to your preferred language.
    Credentials configured for the translation service provider under Connections & Credentials are not valid. Credentials are missing or invalid. Contact your administrator.
    Text to be translated has exceeded the maximum length supported by the default translation service provider.​ Text has exceeded the maximum length.
    Error during translation. Possible reasons are:
    • Credentials configured for the translation service provider under the Connections & Credentials sub module are missing.
    • Translation got timed out.
    • Any other issue with the translation service provider. For example, the exhaustion of credentials for more transactions.
    Unable to translate.

    Error messages on translator configuration

    Table 2. Translator configuration
    Scenario Error message
    When there is no valid subflow associated with the translator configuration. Either a detect or a translate subflow is required for a valid translator configuration.
    When multiple language code mappings are selected for the same language code Multiple language code mappings cannot be selected for the same language code(s): xx.