Emi Amber 

I think you're confusing concordance results with a TM search match.  The concordance is based on finding a part of your text in the TM and returning a match based on how close the part it found was.  So in this case the text you entered in the concordance search matched exactly a part of the TU in your TM, hence it gets a 100% match.  This is not reflective of a match for the whole segment:

The AT is a machine translation, presumably triggered because you have your TM search results set so high that AT takes precedence when the TM doesn't contain a high enough match for the whole segment.  So if you lower this value for example, try 50% just for a quick test, then you should get a TM match instead of AT from Google:

Also... just in case... make sure you have both these boxes enabled in your project settings.  I imagine you do, but worth a check!:

Emi Amber 

I think you're confusing concordance results with a TM search match.  The concordance is based on finding a part of your text in the TM and returning a match based on how close the part it found was.  So in this case the text you entered in the concordance search matched exactly a part of the TU in your TM, hence it gets a 100% match.  This is not reflective of a match for the whole segment:

The AT is a machine translation, presumably triggered because you have your TM search results set so high that AT takes precedence when the TM doesn't contain a high enough match for the whole segment.  So if you lower this value for example, try 50% just for a quick test, then you should get a TM match instead of AT from Google:

Also... just in case... make sure you have both these boxes enabled in your project settings.  I imagine you do, but worth a check!:

Thank you once again!

We solve this by setting a penalty to the Machine Translation.