FIXED? (S)FTP connections not auto re-connected upon saving remotely
Posted: 02 Sep 2022 04:42
Hello
Twice over the last two days I've noted a problem saving remotely. Randomly - or perhaps simply due to some sort of timeout / drop in the SFTP session that AFAIK RJTE maintains in the background (until it's not, which seems to be caused by more than this/one scenario, I think) - the connection appears to die and trying to save a file produces the seemingly generic files did not save properly message. Instead of just prompting to renew the SFTP connection ... or better still, remembering per-file/tab which SFTP profile was used to open the file and transparently, automatically reestablishing any broken connection and just save the ruddy file as expected.
Be great if this could be looked into as SFTP problems, though fewer and far between than in the past, have a nasty habit of crasheezing the app to the point of requiring Task Manager End Task killing. Although in the two occasions I mentioned, only once was the impact that drastic.
Twice over the last two days I've noted a problem saving remotely. Randomly - or perhaps simply due to some sort of timeout / drop in the SFTP session that AFAIK RJTE maintains in the background (until it's not, which seems to be caused by more than this/one scenario, I think) - the connection appears to die and trying to save a file produces the seemingly generic files did not save properly message. Instead of just prompting to renew the SFTP connection ... or better still, remembering per-file/tab which SFTP profile was used to open the file and transparently, automatically reestablishing any broken connection and just save the ruddy file as expected.
Be great if this could be looked into as SFTP problems, though fewer and far between than in the past, have a nasty habit of crasheezing the app to the point of requiring Task Manager End Task killing. Although in the two occasions I mentioned, only once was the impact that drastic.