Added to TODO.

ok, thanks for that missing information with the two connections.
it must be as you say. i am losing the main connection.

but the problem/result is still the same: the queue is lost.

i now set up winscp for that specific server with:
executing dummy protocol commands, all 10 secs
and server response timeout: 25 seconds.

i tested that scenario yesterday some hours, with not losing the connection. (nor the queue, but please be aware, that the problem above is still a matter *if* the (main)connection is lost. i.e. disconnection through the isp)

thanks, loth

From your description, I believe that you lose the main connection. In such case WinSCP drops everything including all background transfers. That's also why you do not see what file caused the problem, because there was not file.

I may be able to help you how to avoid loosing connection. But it is hard when I do not know exact error message. I suppose that setting up keepalives might help.

I'm more than sure! i had this more than 20 times. With a queue of 1 file or a queue of 20 files.

but maybe i'm not clear with my words :-)
so i try again:

i have a queue of 20 files. they transfer in background from here to the remore server. (it doesnt matter if the files from one folder or from different folders)

if the connecton (from here to the server) is lost then the only window (of winscp) i see is: "the connection is lost. OK or RECONNECT or EXIT" (not exactly, but i dont remember the correct dialog now)

after i click on RECONNECT, and winscp connected to the server again, the queue is gone. (i always click RECONNECT because i would like winscp to reconnect to the server and continue with its queuue. maybe i'm doing something wrong here?)

acctually here comes another thing i reccon as a "bad feature":
the winscp window is mostly in background. some other windows are in front, while i'm working.
if the connection is lost, winscp tries to get in contact with me with blinking in the taskbar. now i click on the taskbar-winscp-icon. but if the connection is lost i cannot see on what file or what folder.
the only window i see is the one mentioned above. (ok, reconnect, exit)
it would be more informative if the user could see, on which files the transfer stoped.

hope the fist part makes thins clearer.

loth

@loth: Are you sure? If the background transfer connection is lost, you should not loose whole queue. Only the one transfer is lost.

martin wrote:

Do you mean that you loose connection of the main session? Or connection used for the background transfer?

second.
sometimes the connection is lost via me and the server.
the background-transfer-queue i started is then lost too.
which means in an example: i have to add 20 files from different dirs again to a new queue, because the old queue is gone.

thanks mate for ya fast reply!

loth wrote:

yes, please add a function to save queues after a connection lost and a reconnect.

Do you mean that you loose connection of the main session? Or connection used for the background transfer?

Thanks for adding that feature but you need to improve it a lot. For instance, it would be nice to see "automatic queue back-up feature" and "queue save&load options" (like in https://www.flashfxp.com/) in case of program crashes or unwanted system reboots.
Thanks a lot.

yes, please add a function to save queues after a connection lost and a reconnect.

my problem is, that i have a very mixed queue of files and if the connection is lost (which appears some time) i have to select all the files and directories again. this is a lot of work.

thanks

martin wrote:

As background transfers (=queues) are one of two most wanted features in current user pool, I'll definitely add this. It won't be in the next version, but hopefuly in the one after.

Thanks for adding that feature but you need to improve it a lot. For instance, it would be nice to see "automatic queue back-up feature" and "queue save&load options"(like in https://www.flashfxp.com/) in case of program crashes or unwanted system reboots.
Thanks a lot.

As background transfers (=queues) are one of two most wanted features in current user pool, I'll definitely add this. It won't be in the next version, but hopefuly in the one after.

Indeed, a queue would be my "top of the list" feature request :)

Yes, a download/upload queue is my most wanted feature.

This should be possible with the WinSCP plugin for Far, if you use the temporary file panel. :)

"Queueing files" would be a *very* nice feature!

Anonymous wrote:

Another +1 on that. Queing and being able to save the queue to a file would be great for my remote scheduled backups.

yes, this would be sweet. Have the ability to create queues load/save them and use these with the schedular someone else requested could make my backups a breeze!

Another +1 on that. Queing and being able to save the queue to a file would be great for my remote scheduled backups.

A Download/Upload queue would be GREAT. That's the only reason I still use CuteFTP. Also, an easy way to create a queue offline (such as through a text file, or macro of sorts) would be even better.

An UPLOAD queue would aslo be as helpful

I've found that one of the 'handiest' features in an FTP client is the ability to create a queued download. For example, if you go to copy a directory, or file, it is added to the queue, and the queue is processed either in the background, or upon command. Queue items can be added, edited and removed, and failed transfers can be automatically requeued. This allows one to set up a large batch download with little difficulty, and a lot of flexability.