I didn't come to this diagram right away—in my first months of working much of what I planned didn't go right. Once, a client sent me 1500 words with a very comfortable delivery deadline. It was to be done on a well-known CAT tool. I sent the job to the translator and forgot about it, considering that everything seemed to be going right. An hour before the deadline, the translator wrote to me that the CAT tool closes every time he saves the files, so he'll need another three hours to complete the job. I was still within the deadline to the client, so I didn't even try to figure out what the problem really was and maybe help the translator. I just pinged the translator every hour and waited for the translation. In the end, the CAT tool crashed, the translator lost all the work progress and had to redo the work completely. I had to ask the client for an extension.
If your linguists tell you that they have a technical problem, don't ignore them and hope that they can figure everything out themselves. Ask them what exactly is happening and offer to help. If you don't assess the issue properly and don't clearly understand the possible consequences, you risk receiving an email that reads: "All is lost! I need an extension to the deadline!"
Even if you choose to give the project to another vendor or work in another CAT tool, you still should help the translator with the technical issue right after the project is over. After the work is done, you'll have time to carefully go through the mistakes the translator could have made that led to the system crash. This will help you prepare the linguist for the next job, when they will not fail you, making the same mistakes.