I've noticed this for years too. When it starts happening I restart Trados Studio and that seems to fix it.

I have a similar issue with term recognition not working consistently with 2021 (2017 and 2019 were the same). I already tried to uncheck lookahead, restart Studio, change the layout of the TB window, but nothing helped.

The recognition works for some of the first segments and suddenly stops working for the next segments, then works again for some segments (if I am lucky) and so on. It moreover does not always recognises all words in a segment, even if the terms are all present in the TB.

I sincerely hope there is a way to fix this, since it is a real massive loss of productivity!

Same problem here, too, and I have also had it in all versions of Studio, up to the latest version currently available.

Same for us here. And re-organizing TBs is not an option, as we're using GroupShare and server TBs. Even then, term recognition does not work properly, much to our translators' aggravation as TBs are crucial to translation quality and coherence when working in a large team. 

Same issue here.  Have you managed to resolve it or find an alternative? Thanks

I also have the same issue. Sometimes I only need to close Studio but most of the time I must reorganise the termbase and then it works for the next few segments - and then fails again. 

Yes, I have the exact same problem. I was working away fast in Studio, adding terms, getting them recognised in my document.

And now, one hour later, I am again wasting valuable time trying to work out why Studio has stopped recognising terms.

First it stopped recognising new terms.

Now it has stopped recognising any terms.

And, for the icing on the cake: MultiTerm crashes while trying to reorganise the term bank.

Getting really tired of this buggy software suite...

I shall now have to switch to memoQ to get my work done and then reimport the termbase later.

I also have the problem that MT sometimes crashes while reorganising. This sometimes occurs when the TB is open in Studio, If this not the cause, the only solution I have found is to recreate the TB with Glossary Converter. I find a bigger problem with Verify that flags far too many false positives because it does not seem to calculate weightings correctly.   

Thanks for your comment Anthony. I've now tried it a third and fourth time and suddenly, it worked.

Now Trados is also recognising the terms again. But some terms now throw the well-known "Object not set to reference..." error. So I have maybe now lost terms or at least comments I made on them. Good job I made a backup before reorganising.

The worst thing about Verify is if you have set up forbidden terms. Then Trados finds them *all* in your target text, regardless of what is there in the source segment.

IMHO, terminology handling badly needs an overhaul.

Hi Edward,

Im just linking the two threads together as these are relating to the same issue-

community.sdl.com/.../multiterm-crashes-without-an-error-message-when-trying-to-reorganise-a-termbank