@fpakzat Would need to see more of the error and/or your syntax for the script. It can fail for many reasons.

Hi @fpakzat The system user might not have access to that file path. See https://knowledge.safe.com/questions/3881/fme-workbench-on-windows-scheduler.html and https://knowledge.safe.com/questions/67628/fme-batch-file-works-but-not-via-windows-task-sche.html for ideas of how to work around the Windows Task Scheduler.

@fpakzat drop another line here of those links from danstasafe don't help. I use task scheduler, flat files and call fmw with .bat scripts on a regular basis. Maybe i can help.

I think I found the reason. I got away with this problem by using the path follows UNC standard. I didn't realize the previous path that I used contains a Mapped Drive. 

\\servername\path