WinSCP command doesn't execute in scheduled batch file intermittently

We have a batch file, runs every 4 hours via Task Scheduler, but occasionally when it gets to the part in the batch where it executes the WinSCP command, it just stops there. I have the batch file set to send output to a log file so I can troubleshoot, along with another log file for any connection issues (added recently when this issue started appearing). This is the last part of what shows up in the log file. Anything in the log file after this is from the next scheduled run.
Any ideas as to why this does not execute sometimes? I do have the task set to end after an hour if it is still running, and the task does keep running until it is killed.

All of the settings are what I have gotten from research here troubleshooting other issues and it's been working fine for several months. I have been thinking that this might have come because of a Windows Update.

WinSCP version: 5.19.4, I do plan to update soon, I have a Change order in for that.

Is the ConnectionLog.txt created? Can you post it?
If not, does WinSCP.com output anything? Is there a stuck winscp.com/winscp.exe process?

Hi Martin, thank you for replying.

Yes, it is created, but nothing gets dumped into this file when it doesn't run. Basically the command is executed in the batch file, but nothing happens. It just stops there. The log file I create from the batch file doesn't contain anything further until the next time it runs. I haven't checked to see if there were any stuck processes, I'll make certain to do that the next time this happens. It's random that it doesn't work, so I'm not always around when it doesn't.

Did update to the latest version of WinSCP. This does not appear to have changed the issue.

Hi Martin,

It finally happened again when I could check it right away. No output, no stuck process.

The command seems to get executed from the command line script, but doesn't process. And it's totally random.

Try logging your batch file output as shown here:
https://winscp.net/eng/docs/guide_debugging_scheduler#output

And of course, this has not happened since then. I do think this was an issue that was introduced by a Windows update and that the recent Windows updates may have corrected whatever the issue was.

I'll keep a watch on it, but otherwise, nothing new to go on.

Thank you very much for answering my question and providing me leads to look at.