AutoSuggest works fine but stops working when Studio is restarted

I'm testing the new 2026 version and have encountered a strange bug.

When I add an AutoSuggest dictionary to a project and start working, everything seems fine.

However, when I close Studio and reopen it later on, the AutoSuggest dictionary isn't recognized any longer (even though, naturally, the settings are all as they were before closing Studio).

I don't think there's much I can do about this on my side but I would like to know if this problem is known and if I can expect a fix in some future release.

If not, I will have to stick with my present 2022 version where AutoSuggest works just fine.



Removed AI Suggestion
[edited by: Nadja Balogh at 7:28 AM (GMT 1) on 10 Jul 2026]
emoji
  • Hello,

    Thank you for sharing your experience with the new Trados Studio 2026 version. It seems like you're encountering a specific issue where the AutoSuggest dictionary is not being recognized after restarting the application. While this behavior is unusual, let me guide you through some steps to address it and provide insights:

    ### Step 1: Verify AutoSuggest Dictionary Settings

    - After restarting Trados Studio, navigate to **File > Options > AutoSuggest** and confirm that the AutoSuggest dictionary is still listed and enabled for your project.

    - If it is listed but not functioning, try removing and re-adding the dictionary to see if it resolves the issue.

    ### Step 2: Check for Updates

    - Since you're testing the 2026 version, ensure that you have the latest updates or patches installed. Updates often address bugs and improve functionality.

    ### Step 3: Test with a New Project

    - Create a new project and add the same AutoSuggest dictionary to see if the issue persists. This will help determine if the problem is project-specific or a broader application issue.

    ### Step 4: Reset User Profile

    - Sometimes, user profile settings can cause unexpected behavior. Resetting your user profile to default settings might resolve the issue.

    emoji
  • We will be pleased to help you with this problem so have logged a support case on your behalf. We do prioritise customers who have a support contract so please keep in mind it could take up to 48 hours, especially over a weekend, but rest assured we will contact you as soon as we can. You will be contacted at the email address used for this Community. Support Case Id : CS0054370.

    Anca Stoian RWS Group

    emoji
  • Hi  , I am not sure whether you received my emails sent via the Support case. As mentioned there, this is indeed an issue in the latest versions of Trados Studio (2024 & 2026). We logged it for Development (as CRQ-45016), so it can be fixed in a future update.

    The good news is that there is a workaround to get AutoSuggest working again in Studio 2026 as well. You only need to close and reopen the file in the Editor, without making any changes.

    emoji
  • Hello Edith,

    Thank you for your reply. Unfortunately the problem pops up now even with newly created projects, and closing and reopening the file doesn't necessarily solve the problem either. It's just all very shaky. I'm afraid that I will need to revert back to version 2022 until this issue is properly solved.

    emoji
  • Hello  ,

    Can you please provide details via the Support Case in what circumstances reopening the file does not solve the issue? You can revert to Studio 2022 if you like, but please keep in mind that engineering and technical support for this version will end on 31.12.2026.

    emoji
  • Hi Edith,

    Unfortunately not, it just happened at one point but it is not reproducible and I cannot recognize any patterns. Most of the times it works. It is just a little exhausting to always be on the watch. I'm now thinking of keeping both versions (2026 and 2022) active because even though the AutoSuggest in 2026 is shaky I find that the suggestions generated during the project from the file and the TM (sorry, I don't know what these are called officially) work very well.

    emoji
  • Hi Nadja,

    I understand. The issue was logged as a high priority item, so hopefully a fix will be implemented soon, and there will be no need for the workaround.

    emoji