DaveBarrett wrote:

Anonymous wrote:

I took this "When SessionOptions.Timeout is longer, its value is used instead." to mean that option wouldn't be used and it would use the 120 secs instead.

Can you confirm this is true as it doesn't appear to be behaving this way?

It does behave that way, but only after connection is established. So it has actually no effect on Session.Open.

What is the syntax of the Session.Timeout value if I need to change it from the default 1 minute (it says it is not recommended to change this)

It's TimeSpan.
In PowerShell, you can use New-TimeSpan:
https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.utility/new-timespan

Anonymous wrote:

I took this "When SessionOptions.Timeout is longer, its value is used instead." to mean that option wouldn't be used and it would use the 120 secs instead.

Can you confirm this is true as it doesn't appear to be behaving this way? What is the syntax of the Session.Timeout value if I need to change it from the default 1 minute (it says it is not recommended to change this)

I took this "When SessionOptions.Timeout is longer, its value is used instead." to mean that option wouldn't be used and it would use the 120 secs instead.

You need to set Session.Timeout:
https://winscp.net/eng/docs/library_session#timeout

We are having intermittent issues with WINSCP timing out. Have set timeout to 120, but times out at 60. "Waiting for request event" is repeated. Can you please help with the timeout setting and also why the timeout occurs? Also, response log file isn't created although user has full control over directory.

WinSCP 5.13.0.0
Win 2008 R2
SFTP
PoSH Script
Session Log attached