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.
Do you use Alteryx in a language other than English? If so, we want to hear from you! Please help us improve the international experience of our products by participating in this 5 minute survey.
We are updating the requirements for Community registration. As of 7/21/21 all users will be required to register a phone number with their My Alteryx accounts. If you have already registered, you will be prompted on your next login to add your phone number.
If a workflow fails because a file was not found, it can be discouraging. In this article, we cover some of the best practices to prevent this error as well as some troubleshooting tips if it occurs despite best practices being followed.
Error: Can’t find the file: “[path\FileName]”. Make sure the file path is correct.
In versions prior to 2021.1.4, you will see the shorter message
Error: File not found "[path\FileName]"
Alteryx Designer or Alteryx Server or Alteryx Analytic Hub
This error can occur associated with a range of tools, but the most common are Input Data, Output Data, or Dynamic Input tool.
Alteryx cannot access one or more files that the workflow requires.
First, verify that the file is specified correctly in the tool.
Check that the file is in the expected location.
Verify that the file name has been specified accurately, including file type extension.
Next, make sure that Alteryx is configured to have access to the location.
In the above example image, the path to the desired workflow includes a mapped drive letter (Z:) This is not the best way to designate a path when writing a workflow. Instead, best practice is to use a UNC path. A UNC path has a format that gives the hostname as well as the directory structure in which the desired file is located, for example
If you have used a mapped drive letter instead of a UNC path, the workflow will probably run correctly from your desktop Designer because you are running from your own account, but this is not the best practice because if you ever share your workflow with a colleague or schedule it to run automatically or publish it to a gallery, you'll find that running the workflow in the new environment causes it to fail. You can change the paths in your workflow using Options > Advanced Options > Workflow Dependencies.
You can use the All UNC button to change the paths to UNC paths, and if you desire, you can also test the location to confirm. Click OK to make the change in the workflow.
In the scenarios noted above, the colleague or the AlteryxService must have permission to access network shared resources, even with the UNC path. There is more information on configuring Desktop Automation or Server to grant appropriate permissions in other articles.
More subtle considerations
The path length cannot be longer than 260 characters.
If the workflow is running from a gallery or has been scheduled, then there are a few more restrictions. That is covered in a separate article: Error: File not Found in Staging Directory