Hi Michalis Lioudakis , this behavior (the factory’s CreateTerminologyProvider not firing for subsequent termbases) can happen when Studio treats multiple termbases under one provider instance, rather than instantiating the factory for each separately. Without having access to yr code project, here are a few suggestions and checks that may help:

• If two or more termbases have identical URIs or connection strings, Studio will reuse the same provider instance instead of spinning up a new one.
• I'd recommend to add simple logging as opposed to just depending on the Breakpoints; depending on how you have impelmented this, it's possible that the breakpoints might be bypassed?

Hello again Patrick Andrew Hartnett , unfortunately neither of these solutions helped me find the reason why the factory's CreateTerminologyProvider does not fire up. Logs seem to have the same behavior with the breakpoints and I tried assigning random URIs to our termbase, but the same strange behavior still occurs. Any other suggestions you may have, would be much appreciated.

Hello again Patrick Andrew Hartnett , unfortunately neither of these solutions helped me find the reason why the factory's CreateTerminologyProvider does not fire up. Logs seem to have the same behavior with the breakpoints and I tried assigning random URIs to our termbase, but the same strange behavior still occurs. Any other suggestions you may have, would be much appreciated.