...
Before creating a ticket, however, make sure you have a good understanding of what TM reindexing is and what details to include on the ticket form. You will find this information in the relevant article: Reindexing of translation memory.
TM export file cannot be downloaded because of the file generating endlessly
Solution: Sometimes if the file is huge, the generation takes much longer than usual. Wait a little until the generation stops. It should download immediately afterward.
Tags that are visible in XTM Workbench are not displayed in TM → Manage, in the XTM Cloud UI
Solution: By default, in the TM database, we do not show start and end inline tags at all. We only show them in two situations:
Order of inline tags was changed in the target segment → We show them to indicate that some inline tags have been moved.
Some text was additionally added after the inline tag, in the target segment, which is at the end in the source segment → Basically, it is the same situation as the first one: the inline tag was “moved”, so we indicate start and end inline tags for both source and target segments.
XTM Cloud also groups those tags in TM by default, and only ungroups them when we add something in between inline tags in the target segment.
Date modified and modified by does not correlate in the TM metadata – the linguist did not work with us anymore on that date
Solution: The only change that was performed on the date mentioned in the TM Metadata was the change of the context. Keep in mind that the change of context does not result in an update of the Modified by field, which is expected behavior. The Modified by field is updated only in the case of a change in translations or a change in the status of the TM match, which is introduced to show the actual translator/approver who has created/approved the translation, and not the user who simply accepted a 100% match, which only adds the additional context to the TM match.
TM matches from the previous project are not automatically set to “Done”
Solution: It might be the case that many of your TM matches come from not approved TM. Segments populated with not approved TM matches are only marked as “Done” when you set it so during the project creation stage. Therefore, your default configuration probably does not set such TM matches as “Done”, so if a project manager creating the project did not change that configuration, those TM were left as incomplete.
...
The matches from import are not showing up in the project
Solution: Juxtapose the language combination used for the project and the one from the import, and check if they are consistent.