12-11-2018 09:16 AM - edited 07-22-2021 12:42 PM
This article is an extension to the community article "Scheduling as a copy in the Scheduler DB vs On Disk", and is specifically aimed for Designer + Desktop Automation installations only.
Problem
Whenever I schedule a workflow to run on disk, it executes and finishes with status "Corrupted".
Solution
A few things to check first:
If you responded yes to at least one of these questions, you should make sure all paths (opening/saving workflows, referencing resources…) are UNC.
If you have mapped network drives but don't know the corresponding UNC, you can run the following command in a command prompt (Start> Run> cmd.exe) to list your mapped drives and their UNC paths:
net use
If the issue persists after changing the paths to UNC, the next thing to check is your service account settings. When a workflow is scheduled on Disk, by default the Alteryx Service uses the local system account (explained here) to do the following:
If the local system account does not have permission to perform either of these processes, the scheduled workflow will fail.
Solving this issue involves setting a different account under which the Alteryx Service will execute the workflows:
This shouldresolve the Corrupted error message for yourscheduled workflow. If it doesn't, please reach out to support through support@alteryx.com.
For savvy users, this is probably obvious, but drive mappings are specific to the user account, so if you type 'net use' from the wrong directory, you might not get the information you expect:
Selecting the UNC path can be a bit counterintuitive, but if you are going to "Run the workflow from its original location on disk" it's imperative that you actually load the file from the UNC path before you schedule it. If the location shows as a mapped letter path, it won't work when scheduled.