This often happens to me too. To fix it I just quit Studio and restart it. Then the term recognition window starts working again.

This happens to me very often too, and I fix it also quitting Studio and restarting it. It used to happen also with Studio 2019. Sometimes I need to do this more than 10 times a day, so it is very upsetting and time-consuming. There should be a quicker solution, like a "Termbase revival" button, or, if it is a Studio bug, it should have been corrected by now, but Studio developers seem to ignore this problem. (I am using Studio 2021)

I definitely think that this a clear and present issue (existing terms not showing in "term recognition" in Studio 2021, 2019) is simply a programming issue in Studio. Your termbases are most likely in good shape. I think you need not "reorganize" or do anything with your termbases. That is simply a waste of time. On related topics, I am certain that SDL Studio and SDL MultiTerm have limited capabilities to deal with SDL termbases, for instance, searching a termbase is usually a slow and not always fruitful process. That is the reason why, of necessity, I created Tb-Scout v2.0 (version 1.0 was released back in 2017). I did not just complaint, I created an effective and practical solution (that is my style of work, in general): https://tbscout20.translationist.com/.  Try this, just one of the many evidences I have to my claim. Open SDL MultiTerm Desktop, open a termbase, one with, say, 30,000 terms,  run an "Advanced Search" and look for duplicates. SDL MultiTerm Desktop may take minutes to complete the task and then finally show a crammed list, whereas with Tb-Scout v2.0 it will only take a few seconds (seconds!) and will provide you with a neat and clickable list that will land on that term directly in SDL MultiTerm Desktop.

Please be careful with your content.  The solution suggested by Ali did work so there was no need for your post at all, and you are verging on too much self promotion in here which will be frowned upon and does raise complaints.  It's absolutely no problem to share your solution if it will help solve a particular problem.  But that isn't the case here for at least the following reasons:

• Tb-Scout isn't free - just noting this as you have not mentioned it
• Tb-Scout isn't integrated with Studio so isn't a solution to this users problem anyway
• better alternatives to work interactively that might be worth investigating would be these for example:
  • TermExcelerator - use Excel as your termbase if you just have simple glossaries and get term recognition in Studio - FREE
    https://appstore.sdl.com/language/app/termexcelerator/534/
  • RyS Termbase & Translation Assembler - uses another kind of database capable of handling millions of terms and is very fast, also gets you term recognition in Studio - PAID
    https://appstore.sdl.com/language/app/rys-termbase-translation-assembler/766/

So one free and one paid.  Might be worth investigating.

It might also be worth looking at Language Cloud for Trados Studio 2019, or SDL Trados Live Essentials for Trados Studio 2021, where you have a cloud based terminology solution at your disposal and this is also interesting.

But having said that... MultiTerm isn't that bad.  Definitely rough around the edges but quite flexible and good enough for the majority of users once you get used to its quirks.  Can always be improved however.

Please be careful with your content.  The solution suggested by Ali did work so there was no need for your post at all, and you are verging on too much self promotion in here which will be frowned upon and does raise complaints.  It's absolutely no problem to share your solution if it will help solve a particular problem.  But that isn't the case here for at least the following reasons:

• Tb-Scout isn't free - just noting this as you have not mentioned it
• Tb-Scout isn't integrated with Studio so isn't a solution to this users problem anyway
• better alternatives to work interactively that might be worth investigating would be these for example:
  • TermExcelerator - use Excel as your termbase if you just have simple glossaries and get term recognition in Studio - FREE
    https://appstore.sdl.com/language/app/termexcelerator/534/
  • RyS Termbase & Translation Assembler - uses another kind of database capable of handling millions of terms and is very fast, also gets you term recognition in Studio - PAID
    https://appstore.sdl.com/language/app/rys-termbase-translation-assembler/766/

So one free and one paid.  Might be worth investigating.

It might also be worth looking at Language Cloud for Trados Studio 2019, or SDL Trados Live Essentials for Trados Studio 2021, where you have a cloud based terminology solution at your disposal and this is also interesting.

But having said that... MultiTerm isn't that bad.  Definitely rough around the edges but quite flexible and good enough for the majority of users once you get used to its quirks.  Can always be improved however.

Paul said:

Please be careful with your content.

My content is perfectly legitimate, based on facts. This comment about my comment to me is tantamount to censure.

Paul said:

Tb-Scout isn't free - just noting this as you have not mentioned it

The demo version has in and of itself a decent level of functionality. Anything wrong with charging for my work?

Besides, I offered you and SDL staff a free Product License Key to which you did not reply. 

I've contacted a number of people before saying basically please help me take a look at the newer version of my application and I'll give you a free license. If someone contact me in a friendly manner I have no problem giving away a free Product License Key. I don't work just for money. I love what I do and I have plenty to share.

Cheers!

Ozzie

Unknown said:

This comment about my comment to me is tantamount to censure.

Well... if it was I would have simply removed it.

Unknown said:

On related topics, I am certain that SDL Studio and SDL MultiTerm have limited capabilities to deal with SDL termbases, for instance, searching a termbase is usually a slow and not always fruitful process. That is the reason why, of necessity, I created Tb-Scout v2.0 (version 1.0 was released back in 2017). I did not just complaint, I created an effective and practical solution (that is my style of work, in general): https://tbscout20.translationist.com/.  Try this, just one of the many evidences I have to my claim. Open SDL MultiTerm Desktop, open a termbase, one with, say, 30,000 terms,  run an "Advanced Search" and look for duplicates. SDL MultiTerm Desktop may take minutes to complete the task and then finally show a crammed list, whereas with Tb-Scout v2.0 it will only take a few seconds (seconds!) and will provide you with a neat and clickable list that will land on that term directly in SDL MultiTerm Desktop.

What does this have to do with the original posters question?  If all the software developers who sell their solutions started to do this by commenting out of context in posts where users were looking for help I'm pretty sure we would have users complaining.  For me this is pure advertising which I have already seen you do in here and I have not censored you:

https://community.sdl.com/product-groups/translationproductivity/f/openexchange_applications/31397/a-new-and-practical-way-of-searching-finding-and-exporting-sdl-termbases-meet-tb-scout-v2-0-the-sdl-multiterm-explorer

I even shared it!

I am just asking you nicely to be considerate with your posts and advertising for a product you are trying to sell.

Paul said:

But having said that... MultiTerm isn't that bad.  Definitely rough around the edges

Paul, you just have not tested it.

Unknown said:

The demo version has in and of itself a decent level of functionality. Anything wrong with charging for my work?

Besides, I offered you and SDL staff a free Product License Key to which you did not reply. 

I'm finding it difficult to understand why you are reacting this way.  I didn't reply to your email on the free keys yet because they aren't of any use for us as you know.  We use 64-bit versions of Office and we don't use Office 365.  So we can't even test how useful your product is.  I also have plenty to do and don't reply quickly to all the emails I get.  I did however spend part of my Sunday fixing your submission and improving it aesthetically and publishing it for you.

I really think you should stop now.