2019 SDL  takes too long to give translation proposals when we combine searches in the two resources, translation memory and machine translation. And as an explanatory note, if the segment we are working on does not have any result in memory, the plugin goes well (or so it seems); The problem is when there are results in the translation memory.

There is some kind of conflict that we do not understand, and we would like to solve it as soon as possible.

We have tested the following:

-Translate the same document with the same translation memories and the Machine Translation plug-in for the 2017 SDL version: it goes well.

-Translate the document using only the translation memories in the 2019 version: it goes well.

-Translate the document using only the Machine Translation plug-in in the 2019 version: it goes well.

-Translate the document combining translation memories and the Machine Translation plug-in in the 2019 version: it is not going well.

Did any of you experienced similar issues?

Thank you very much for any clue that you can offer us.

Maddalen