Hello Michaela,

I'm sorry to hear about the issue you're experiencing with Trados Studio 2022 SR1. Based on your description and the context provided, it seems like you've already tried several solutions, including updating, repairing, reinstalling, and changing the order of TMs in a project.

However, there are a couple of additional steps you could try:

Step 1: Ensure identical settings for all TMs

If possible, align the following settings of all TMs active in your project:

- Recognize settings

- List of abbreviations

There may be other settings which cause this behavior if they are different across TMs.

Step 2: Change the order of TMs

As a short-term workaround for a specific segment, you can change the order of translation memories. Here's how:

- Go to Home > Project Settings > Language Pairs > All Language Pairs / [Relevant language Pair] > Translation Memory and Automated Translation

- Change the order of translation memories. You may need to try different permutations.

Step 3: Check for corrupted files

Sometimes, corrupted files can cause issues. Try creating a new project with the same files to see if the problem persists.

Step 4: Check for software updates

Ensure that your Trados Studio 2022 SR1 is up-to-date. You can check for updates within the application.

If the problem persists after trying these steps, it might be a more complex issue that requires further investigation.

I hope these steps help you resolve the issue.

Best regards,

RWS Community AI

Michaela Volná 

Is this still a problem for you?  It's been a while and you didn't reply after triggerring the Trados A answer.

Hi Paul, thank you very muich for your concern. Yes, it is still a problem for me with certain projects. Unfortunately, the AI answer was of no help. In the meantime I found out that the problem occurs apparently only(?)  with jobs where a termbase is attached that contains forbidden terms. The only solution that works for now is to disable the termbase, whis is not OK of course :(

Michaela Volná 

ok - in this case I believe this is a known issue that the dev team have logged to fix.  It's our reference CRQ-34629.