over time, time increase bumps have helped. 12 min was working, now up to 24 min,. no time outs.

So did you try to set the timeout to a way longer value?

yes way after 3 min, I will not see the log for a while. The last logs created and last modified date was about 1hr,
this is a 2+ TB job to sync an already seeded dir. It was working with no real issues before while running right after syncing multiple dirs in the same script. even after splitting it out to its own script it gets the timeout.

How long does it take before you get the error? Is it more than those 3 minutes?

Hello, I am getting the attached error.
thanks in advance for any help.

Error: Exception calling "SynchronizeDirectories" with "7" argument(s): "Timeout waiting for WinSCP

I have been getting this error lately while trying sync dirs. I do not believe its system resource related nothing pegged when running.
Winscp 5.14 8780
2012 r2, 16GB of ram, 12 virtual processors.

I have tried to keep the connection open longer.

{$sessionOptions = New-Object WinSCP.SessionOptions -Property @{
Protocol = [WinSCP.Protocol]::Sftp
HostName = "167.19.x.x"
UserName = "ServData"
Password = "password
SshHostKeyFingerprint = "ssh-rsa 2048 p4k2wWh76DLMzm1710RkfcMvt6i16ZqGYgi3zbuC9Co="
Timeout = '00:03:00'
}

$session = New-Object WinSCP.Session -Property @{
Timeout = '00:03:00'
}