I have this bug too, which is intermittent and seems to happen after auto-propagation has propagated some segments. Term recognition then stops abruptly.

Together with other bugs in terminology, which I've also reported here and which remain unfixed, Studio is effectively useless for terminology now. I'd respectfully suggest fixing these serious bugs before adding yet more features to a product already groaning under the weight of unrectified issues. Unless the new AI features are somehow going to solve these problems.

Regarding your statement, "Together with other bugs in terminology, which I've also reported here and which remain unfixed, Studio is effectively useless for terminology now.", I totally agree.

I have long since been unable to use Studio in my daily work translating because whether or not term recognition will work seems to be totally random, and always has been. I have been using Trados Studio since the murky beginning of time, and always end up giving up on it in disgust after a few weeks of giving it yet another try.

I really doubt the issue reported in this thread is restricted to Asian languages. I suspect it's just the age-old problem rearing one of its myriad serpentine heads. Mark my words, hell will freeze over before the RWS team manage to fix this pesky problem. 

I have tried every trick in the book to get reliable term recognition working in Studio:

• the built in MultiTerm termbases (problem persists!)
• RyS Termbase & Translation Assembler (RWS app, now called ‘RYSTUDIO Post-editing Package’)(IYAM, the best/only way to get reliable term recognition in Studio)
• TermExcelerator (an app that allows you to use Excel files as termbases)(problem persists!)
• the new cloud termbases (problem persists!)
• using external term lookup software like GT4T’s Simple Glossaries (not really practical)
• using no termbase and relying solely on TM/concordance searching (not really practical)

See also: community.rws.com/.../167933

Actually, the thread was started in order to report this bug as affecting Bulgarian, which is a Cyrillic language, so the loss of functionality is not limited to Asian languages.

I am stunned that RWS is not prioritizing this, and 4 months later they have not offered a fix... or have they?

I work in German to English, so it seems to be general, not restricted to Asian languages.

As I said above, there are now major bugs affecting a) term recognition while editing (it is possible to search for terms in the current segment that are not flagged in the automatic term recognition for that segment), as reported by OP here; and b) term recognition during the quality check with F8 (random terms are seemingly excluded from the check), as reported on this site here:

community.rws.com/.../terminology-verification-in-trados-studio-2022-is-unreliable

I am experiencing the same problems. I heavily rely on Multiterm and use it whenever I can, but it sometimes simply quits, doesn't show terms, shows terms during the F8 check that weren't flagged while translating and I sometimes have to use Termbase search to check if certain terms are in the Termbase or not, just to be sure. Some years ago I upgraded from 2019 to 2021 in the hope that problems would be solved, but unfortunately they haven't. 

This has been my experience when working with Trados for the past 10 years or so, or for as long as Studio has existed:

Term recognition simply stopping working, terms not being shown, completely unreliable F8 check and battling with the equally buggy Termbase search to check if certain terms are in the Termbase or not, just to be sure, again and again and again. Incidentally, has anyone ever gotten the keyboard shortcut for Termbase search to actually work? What a sad joke!

In memoQ, I can click Ctrl+P and I immediately search my termbases and edit terms as well.The system is 100% reliable and instantaneous.

It's insane that the so-called market leader is this bad at handling terminology. And what's even crazier is that we users put up with it. I suppose it just goes to show how few translators actually use termbases.

Each time, I pay the money, upgrade from version to version, and immediately realise that it's all exactly the same old crap, under a new layer of paint.

Incidentally, I may have misunderstood where the problem with Trados Studio's term recognition lies. I had always assumed that it was caused by the underlying technology (Microsoft Access databases). However, now that I think of it, various people from RWS also told me to try the new cloud termbases. They said they would definitely work. Ha ha. I have found that they work just as bad/unreliably as the local MultiTerm-based termbases. The same problem is also present with their TermExcelerator app, the Excel-based workaround. All of this leads me to believe that the problem must lie elsewhere: it's not the underlying termbase tech, but rather, there must be something wrong with Trados Studio itself, which isn't surprising as it is such a mess in general.

Incidentally, I may have misunderstood where the problem with Trados Studio's term recognition lies. I had always assumed that it was caused by the underlying technology (Microsoft Access databases). However, now that I think of it, various people from RWS also told me to try the new cloud termbases. They said they would definitely work. Ha ha. I have found that they work just as bad/unreliably as the local MultiTerm-based termbases. The same problem is also present with their TermExcelerator app, the Excel-based workaround. All of this leads me to believe that the problem must lie elsewhere: it's not the underlying termbase tech, but rather, there must be something wrong with Trados Studio itself, which isn't surprising as it is such a mess in general.

Exactly! How come RWS cannot fix term recognition for so long and why would they not prioritize?

https://www.trados.com/blog/terminology-and-consistency-an-inseparable-pair/

Great marketing, now fix the product.