Ines de Azcarate Maria Leverenz Emi Amber 

Please provide the FULL version numbers you have for Trados Studio AND MultiTerm?

Also, provide the FULL path to where your termbase is being stored.

Same here.

In the last weeks I have a "MultiTerm is unable to add the entry" error message when trying to quick add a term in a Cloud-based project, while working on it from the local Trados editor. 
Trados Studio 2024 - 18.0.2.3255

MultiTerm 2024 - 18.0.2.3266

Probably not what you want to hear, but the termbase system in Studio, both local and the newer cloud-based systems, have NEVER worked reliably, and probably never will. See my blog article on this topic at michaelbeijer.co.uk/trados_tax.

michaelbeijer.co.uk/trados_tax (here's the link again as the previous link was broken)

HI all - you are right that this has been a challenge for us for many years (no beating around the bush here). The potentially interesting news is that for the upcoming Studio 2024 SR1 release (tentative July or August 2025 release date), we have done some very deep changes in our code to bring all of the terminology logic into the Studio code base itself (most of it was living in the MultiTerm code base, and communication behind the scenes between Studio and MultiTerm could become fragile). As one example, this has helped us address term recognition problems where it might not work reliably anymore after a certain time of working. This should hopefully be a thing of the past now. Likewise, we have looked at the code behind adding terms to local, server and cloud termbases. I will not say that everything is perfect now, we are still stabilising this area after making these very extensive changes, but this will now (finally) put us in a position where we can more easily address any issues moving forward. Just as a sign of life from our end.

HI all - you are right that this has been a challenge for us for many years (no beating around the bush here). The potentially interesting news is that for the upcoming Studio 2024 SR1 release (tentative July or August 2025 release date), we have done some very deep changes in our code to bring all of the terminology logic into the Studio code base itself (most of it was living in the MultiTerm code base, and communication behind the scenes between Studio and MultiTerm could become fragile). As one example, this has helped us address term recognition problems where it might not work reliably anymore after a certain time of working. This should hopefully be a thing of the past now. Likewise, we have looked at the code behind adding terms to local, server and cloud termbases. I will not say that everything is perfect now, we are still stabilising this area after making these very extensive changes, but this will now (finally) put us in a position where we can more easily address any issues moving forward. Just as a sign of life from our end.

Hi Daniel,

I appreciate you sharing this. Trados Studio actually has many good things going for it, and if it weren't for its totally unreliable terminology system, I might have used it much more than I have in the past, which is usually only when I am forced to by an agency client. Terminology is vital for me as a technical translator and I need a reliable termbase in my CAT tool, which allows me to add terms instantaneously, and which will show me if a term is in my termbase. If it's in my termbase, I need the system to tell me so. Not sometimes, but always. I therefore very much look forward to test-driving Studio 2024 SR1 release!

Michael Beijer