Alteryx Workflow Scheduler

Kirkitu

Hi,

I want to schedule my workflow which is taking input from excel saved on my system. I am having licence also.

But when I schedule the workflow,after run the status is complete but getting below error-

 Tool #1 Unable to open file for read: C:\...xlsx Error Opening file: C...xlsx: Access is denied.  (5)

Any help on this is much appreciated!!..

Thanks in advance..

fharper

was this resolved?

If not one thing to consider is the what ID is running it?  Is the scheduler you mention the Alteryx Server Scheduler or a standalone designer with Scheduler option?  what is the ID used on that scheduler.  if the file is on "My Own system" you local hard drive then typically most people do not share their local drives to others including the ID running the scheduler.  solution is to put the file to be processed in a folder in a shared location and update the flow to point at the new location which the "production" or "operations" ID can access. 

I do not use the Server version of Alteryx but I do run a separate designer license with Scheduler option to automate our work.  In that scenario I set up a "production" ID or operational account, various places call it various things.  That ID like any other is given access rights to any DBs and folders where I have modules, data and or want to write output to.  We do not share local drives and have a policy against storing permanent data on local drives for security reasons.  the local hard drive is mainly used for software and temp space, Alteryx can eat up temps space on the drive if you run heavy jobs eating lots of data and you run many flows at once so it is good just for that not to write permanent outputs to local drives and eat up the available space for temp files.

Every so often a newbie builds a flow writing or reading from their local drive and then schedules it to run on our production account but forgets to "productionize" and retarget to shared network storage they should have been using to start with.  That issue is a error that sounds like your error.  The account running the module, on the production system, doesn't have access to an individual's local hard drive on their laptop.