Machine translation (MT) – most common issues & troubleshooting


Below are the most common problems clients report in tickets concerning the Machine translation (MT) engines.

When submitting tickets, remember that XTM Cloud is only an intermediary between you and a particular MT service provider. We are not responsible for the quality of the returned text and can only influence the overall process in a relatively small way.

Before reading the article below, we recommend that you read the step-by-step guideline to setting up machine translation (MT): How to enable and set up machine translation (MT).

Before reading the article below, we recommend that you read the step-by-step guideline to setting up machine translation (MT): How to enable and set up machine translation (MT).

Issue description & Solution

MT engine fails during synchronization

Solution: Perform the following initial checks in your MT connection details (administrative privileges required!) before submitting a ticket:

  • Check that no additional white spaces are present.

  • Check if your credentials are correct. If you have another set of credentials, check them as well.

  • Check if your MT engine's API panel permits connections to the outside world (especially Google MT).

  • If nothing happens when you click on Synchronize, or there is an error, open the Dev Tools in your browser and check for error messages (see the following article for help: How to use browser's a developer tools (Dev Tools)?).

MT engine fails to process some of the segments

Solution: Perform the following initial checks before submitting a ticket:

  • Check that you have not hit any of the limits in your MT API. Both the character and time limits are important.

  • Check if the MT engine you are using can match the remaining segments with XTM Workbench mode (we recommend that you select the After analysis and in XTM Workbench option in your MT engine connection details).

  • Check if the affected segments have special characters or similar, which can influence the MT output.

MT engine fails to process all segments

Solution: Perform the following initial checks before submitting a ticket:

  • Check if the MT engine is activated at project level in Project editor → General infoMachine translation.

  • Check the project's Metrics. If there are only ICE, Leveraged and other kinds of matches then your MT is probably configured to ignore such segments and not provide a translation for them. Check your project's General info page (see the screenshot from the previous bullet point).

  • Check if the MT engine has been synchronized correctly and the credentials you are using are correct (see the first issue from this section: MT engine fails during synchronization).

  • Check whether any limits have been exceeded.

  • Ask an MT service provider if a particular language pair is supported by their MT engine.

Note that, if an MT service provider just recently added a particular language pair to their supported languages list, it is likely that XTM Cloud has not started supporting it yet and has to upgrade the required MT functionality. Should that be the case, do not hesitate to contact the XTM International Support team.

MT engine works only in XTM Workbench mode

Solution: Perform the following initial checks before submitting a ticket:

  • Check your global MT settings and verify if the After analysis or After analysis and in XTM Workbench mode is selected.

  • Check if other and smaller files are translated during the analysis.

Google MT has restricted access

Solution: Currently, XTM can only work with Google MT if there are no restrictions set in the Google API panel. As soon as you set a whitelist or other restriction methods, this MT engine will work with XTM Cloud.

Subcontractor cannot use MT engine in projects

Solution: Currently, it is only possible for a subcontractor (LSP) to enable MT in a subcontracted project when the contractor sets the appropriate setting on their side.

While the UI on the LSP side might show that a particular MT is available for switching on in the project General info section, this can be a false positive. For this reason, before proceeding, the LSP should ask their Contractor if the MT engine is indeed switched on.

DeepL MT is not working

Solution: If solutions from the issues above are not applicable, there is another possible approach.

DeepL comes in two versions: V1 (for CAT tools) and V2 (for developers). XTM supports only V1. In your DeepL panel, check if the version of the MT engine there is also correct.

MT blockage

Sometimes, an MT engine might not being able to implement its mechanisms in XTM Workbench. You will then see this system message:

As seen in the example above, the issue occurred with Google MT.

Solution: To resolve this, a Google API configuration must be implemented, to prevent unauthorized use and data theft. You need to configure your API key on the Google and Amazon side and there is an option for that:

You would need to use the "None" or "HTTP referrers (web sites)" options, adding the

URL and other XTM Cloud instances required for the client’s account.

MT matches populate target randomly

Sometimes, certain segments are populated with an MT match straight away while others are not, despite this MT system being specifically configured to only produce a suggested translation and not insert a translation automatically.

Solution: One thing to remember is that running simultaneous projects contributes to ICE or Leveraged matches appearing in the segment. However, the same match does not exist at the time the MT engine is checking for matching segments when you only work on a single project.

MT is a collaborative mechanism: running multiple projects at the same time leads to the generation and display of new matches in the segment.

The "M" status instead of "MT" in the XTM Workbench segment

Sometimes, you might find it hard to understand the M status instead of MT in the XTM Workbench segment when you used machine translation, and, in fact, this is the only match in this segment.

Solution: This is expected behavior if the match has not yet been inserted in the target segment and confirmed. The M status means that the segment in question has matches, but none of them have been used in the target segment. The MT status will only be visible if an MT match is used and confirmed in the target segment.

If you would like to have your MT matches inserted into target segments by default, ensure that [Populate target with match: Always, fixing inline differences] is enabled during project creation:

Client API key is not working for Microsoft MT

Solution: The client's API key might be associated with a particular region, and they must specify their own region. To do so, first contact the XTM International Support team and ask them to implement an option for users to enter a custom 'issueTokenUrl'.

After the Support team changes the configuration in the back-end, the MT connection details form should contain these two additional fields: Translation endpoint URL and Authorization endpoint URL.

In the case of Microsoft MT, a URL of this kind, relating to a specific region, must be specified in the Authorization endpoint URL field.

Keep in mind that the URL practically stays the same, and what is actually changed is the part indicating a particular region. For instance, in the URL: the part westeurope is a variable value.