I know it's a little late for feedback on that issue, and believe me, I am also very annoyed at the bugs that have added up in Trados versions over the years, but I actually found a workaround for that issue, based on your feedback that it happens randomly “when [you] open several files from various projects.” It also happened to me randomly when I had more than one project open. So I tried systematically closing all projects before opening another one, and I never got that issue again. 

I know it's not an ideal solution, but as I said, it's a suitable workaround for me, until the issue is definitely resolved by SDL.

And by the way, thanks to Paul Filkin for his honesty: I prefer being told the plain truth (that he unfortunately cannot do anything about it, but will continue pushing for a resolution), rather than being made empty promises.

Edit: The issue does continue to happen once in a while even when I have only one single-file project open, but it it always resolved (at least for a few days) when I close all projects and reopen the one I need (even if it's the same one that was open).  

I'm working on a project with 30 files open simultaneously, totalling 60k+ words, so it might be a bit of a processing challenge for Studio after some time.

I've noticed that, just like with a few other things in Studio, it often helps to exit the current Editor session you're working in (in this case, with multiple files open), open a different project in Projects View and then straight away open the project and it's batch of files you had previously been working on simultaneously.

I didn't even have to close Studio. As soon as I opened my current project again, after hopping into another random project, CTRL+Z worked again.

Hi Paul, 

As I mentioned in another comment, I know it's probably too late for Adrian Palme's specific case, but since the problem still exists to this day, I will try providing some insights in case it would help find a cause.

• The CTRL+Z issue does not seem to be linked to any specific operation. It just happens, sometimes, that you type a few words and press CTRL+Z and it just doesn't work. I don't specifically remember what I had done in the seconds to minutes before it happened, but my guess is that it may happen when Trados, or the project itself, has been open for some time. Maybe it's because Trados' memory becomes overloaded? Or maybe it can be linked with the computer being put in sleep mode and woken up in the meantime, while the Trados project has remained open? I Thing that would be worth investigating.

• In any case, the CTRL+Z issue seems to be consistently solved (for an indefinite time, usually a few days) when we close all Trados projects. Then, we can reopen the project we were already working on, and the CTRL+Z works again. That is just a workaround, not a solution, but maybe knowing that could also help find an actual solution.

• By the way, thanks a lot for trying to help as best you can, and for being honest when you don't see an immediate solution. I prefer a clear, but disappointing answer to a vague, optimistic promise that will lead nowhere. Keep up the good work!

Just ran into the same issue with the latest release of Studio 2019. I had experienced this in the past too at some point. Reopening Editor helps.

What can I say, SDL...Luckily we have MemoQ. It's not perfect either, but at least never fails you with the utterly basic stuff.

Hello, the thread is quite old, but I was facing the same problem, looking for a solution which is quite simple: CHECK WHETHER YOU ARE LOGGED IN OR NOT. I wasn't logged in, offline, then I did it and all shortcuts were back active. 

Best regards 

Marcin

Seems legit! <facepalm emoticon here> Looks like RWS is continuing the good old traditions of reliability.

Good tip! I'll just try closing the project instead of the entire Studio program and having to wait for it to load again. Thanks!

Hi Paul !

First, as always, let me tell you I really appreciate your honesty. It would be so easy to just beat around the bush with stereotyped cant, yet you state the situation plainly. Numerous users (including me) are dissatisfied with RWS technical support in many ways, but your honesty honours you personally and is greatly appreciated.

Now, with the issue at hand: it is indeed a recurrent problem that CTRL+Z regularly stops working, and the only “common denominator” I could find is that it happens when multiple projects are open in the Editor. 

It typically does not happen right away. It happens when there have been more than one file open in the Editor and you have continued working in one or more of the files.

By experience, I'd say it WILL necessarily happen after some time, but it could take days... or just minutes. I know the recommended practice would be to restart the computer every day, but given that there are occasional network problems that make restarting Trados Studio impossible AND it tends to happen at the worst possible moment (Murphy's law), many of us in my organization prefer to keep it open for the whole week.

Of course, restarting the program is a workaround, but the BIG problem is that you don't know when the CTRL+Z dysfunction will occur, and if it happens to occur when you made a major error and want to correct it, it may cost several minutes of work.

Anyway, if you want to reproduce the issue, all you have to do is open, say, three or more different projects at the same time in the Editor, type and confirm segments for a while, switch project and do the same (without closing the other projects), then “rince and repeat” untill CTRL doesn't work. Unfortunately, I can't say how much time it could take, but it will almost certainly occur.

Hope this helps, and thanks again for what you do as the communication channel between consumers and other RWS officials. 

Hi Guys! My experience has been that whenever I make an error, like hitting two keys by accident, that the CTRL+Z stops working. It has happened variously in single files and with multiple files, but I usually don't have more than one project open at one time, so that doesn't seem to be what is triggering the error. There really doesn't seem to be regularity to me. It's a big drag when you loose a whole segment you just worked on and have to reboot Studio all over in the middle of your concentration...Thanks for the input! Deborah

Paul, I'm happy to inform you that this bug persists in 2024 and I have been experiencing it for years without making a post about it.

Your classic "works on my machine" responses are really aggravating. I understand you feel helpless but the sarcasm and gaslighting in your responses are totally unacceptable.