Philippe Riondel 

Just because the title of an error message looks familiar doesn’t necessarily mean it’s caused by the same issue as one from 10 years ago. We are continuously working on fixing bugs, often even before they’re reported, especially if you've agreed to share telemetry data with us. This data helps us capture error stacks, including those that don’t necessarily interrupt your work, and allows us to focus on the areas where we can make the most impact.

It’s clear that experiences vary—some users rarely encounter issues, while others experience them more frequently. Naturally, forums like this tend to attract users who are seeking help, reporting bugs, or expressing frustration, which sometimes skews the perception. Even so, we take this feedback seriously and use it to help guide our development efforts. For instance, we employ topic modelling to identify recurring themes from forum discussions, and we've utilised OpenAI’s GPT-4 to help analyse and interpret the results. This provides valuable insights, though it can be challenging, as users may not always know the best way to frame their questions or what information to provide that is helpful for troubleshooting.

We understand that the range of products we offer and the ongoing development efforts behind them adds complexity, but we are fully committed to addressing these challenges and ensuring the software works as expected. While you shouldn’t have to worry about the inner workings, we want you to know that these efforts are constant.

We truly appreciate feedback like yours. It’s encouraging to see constructive thoughts on how we might address challenges, especially with the use of AI. Thank you for your engagement—it's great to see we are aligned in our approach to tackling these issues.

Hi Paul,
Thank you for your answer. Be assured my aim was constructive. I do not know a lot about AI, since it's just emerging, but from what I guess, an embedded AI functionality may be able to monitor and analyze processes from inside in real time as a background task, point out the exact issues and either proposing a turnaround to the user or send its findings to your teams.
Regards 

Also, I generally agree to sharing telemetry data in order to improve the applications I use, and I likely have agreed for Studio too. But I am not sure to know where to check if I actually did it. Would you please remind me where is the option in Studio?   

Very informative answer, Paul , I've learned some stuff I didn't know.

And, Philippe Riondel wow, wouldn't that be great, if AI could inform the user accurately what has caused the same old error message, whether it's Trados or it's something on the user's setup that is triggering the issue. It could lead to longer-term solutions and better understanding by the user.

Bon courage !

Ali 

Philippe Riondel 

Sure... it's here in the Help menu: