Silenced8647 wrote:

Removing the empty line in the script fixed this. Thanks for the assistance!

https://winscp.net/eng/docs/faq_batch_file

[...] For the new-line escaping to work as expected in the batch file, the caret symbol ^ has to be the very last character on the line (no spaces after it) and the next line needs to be indented (at least one space at the front). [...]

Removing the empty line in the script fixed this. Thanks for the assistance!

It behaves somehow mysteriously. I cannot reproduce it.
But as I've posted above, I suspect the format of the batch file. The empty line cannot be there:

Normally WinSCP won't even see the commands after the empty line, as the batch file would consider them to be separate command, not belonging to WinSCP.
I can see in the log that WinSCP actually gets them. I assume it's because that in the actual batch file, the whitespaces are somehow non-standard.

Attached is the full script and log (sanitized for sensitive information)
Thanks for the guidance

Both the code and the log are incomplete. It's hard to help then.

I can only point you to:
Why are some WinSCP scripting commands specified in a batch file not executed/failing?
(particularly to the "New-line Escaping" section)

If you need further help, please post complete code and log.

I'm trying figure out what the problem is with this script. I'm able to transfer a file with GUI – and used the "Generate Code" for the session as a basis for the script.
Authentication is working fine but the target file won't download. I'm not sure if there's a particular parameter to add for timeout or something. Any assistance in pointing me to next steps would be greatly appreciated.
Attached file includes script (less the connection string) and excerpt of log file output.
WinSCP Version 6.5.1 (Build 16311)