This request has been added to the tracker:
https://winscp.net/tracker/1937
You can vote for it there.

Hi Martin,

Could you assign a bug tracker to this?

Regards,
Sander

Hi Martin,

I would like WinSCP to quit with an errorcode when /maxreconnect=9 has been reached.
So at reconnect 10 it can quit.

Something like that?

Regards,
Sander

Yes, this time it is. Because the server keeps failing indefinitely, but allow reconnect nevertheless. So WinSCP indefinitely retries. What would you like it to do instead?

Hi Martin,

Sorry to say this but it is really an infinite loop.
I uploaded a new logfile. This transfer took more than an hour so I aborted it.

Regards,
Sander

I do not see an infinite loop in the log. The script was aborted:

. 2020-12-16 15:22:57.062 Script: Failed
. 2020-12-16 15:22:57.062 Script: Exit code: 1
. 2020-12-16 15:22:57.062 Closing connection.
. 2020-12-16 15:22:57.062 Sending special code: 1
. 2020-12-16 15:22:57.087 Session sent command exit status 0
. 2020-12-16 15:22:57.227 Main session channel closed
. 2020-12-16 15:22:57.227 All channels closed

Using WinSCP Version 5.18 beta on Windows 2016 Server.

Hi,
We are uploading files using command line /command option. We also use a proxy server.
We noticed that if write permissions are incorrectly configured on remote FTP servers, the upload fails. That is OK but WinSCP will retry and enters an infinite loop, which is NOT OK.

See attached logfile for more information.
Any ideas? The option /nointeractive doesn't seem to fix this issue unfortunately.