...
For this reason, the TM match has to be deleted because you do not want to see not approved translation memory in your projects. Therefore, the said TM match gets a warning accordingly.
A Leveraged match transforms into an ICE match
...
Imagine you have a Leveraged match populated during project analysis. Then, in the an XTM Workbench session, a new TM entry appears – an ICE match, which comes from another project with a different source file.
It points to the same TM entry as the Leveraged match, because it originates from the same TM record. You accepted must have confirmed the segment and thus added context to the very same TM entry, according to your global TM settings:
...
Since the The TM entry is has thus become an ICE match, and no longer a Leveraged match, but an ICE match, so it also no longer qualifies as a valid Leveraged match and thus . Therefore, it must get a proper warning in its metadata in XTM Workbench. An , and the ICE match must appear instead.
...