This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.
My guess is that F-drive is a mapped network drive? To my experience it works better to use the full UNC path "\\server\path\your_file". This has something to do with that the scheduler (probably run by another user) does not nescesarrily have a F-drive mapped.
I you dont know where F is pointing you can use the command "net use" to get a list. And of course, make sure the user running the scheduler have access to the network drive.
This is not a network drive, however the problem is exactly what you pointed. The user running Alteryx (different computer in my case), did not had access to file location. The workflow does run manually in this scenario, but will not by scheduler. By providing folder access to the Alteryx user, the workflow runs even via scheduler.
I've been scouring all the topics on this and still cant get my scheduler to run it. Can you offer any other scheduler tips? Ive checked my access to the drive which I have full control, I tried using the UNC path name, I tried renaming the file with no spaces in the name. A lot of man hours on this one still no joy "file not found"... any help would be greatly appreciated