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.
If you are writing to a network drive, don't include output files in the Manage Workflow Assets.
This way the path in the output tool will not be changed to \externals.
You may end up with a new issue. When you run a workflow in the gallery, it runs in the context of the account that is running the Alteryx service on the Gallery server. This account will need to get the write permissions to target directory. By default, the account used for the Alteryx Service on the gallery is Local System. This doesn't have any permissions outside of the server file system.
Check with your Gallery Admin/IT Dept to ensure that
1. the Alteryx service runs with a domain account
2. this account has permissions to write to the target directory.
When you select an output file as an asset when exporting or saving to an Alteryx server, the file "filename.ext" is moved to the path "_externals\n\fllename.ext" where n is an integer generated by an internal algorithm. Any Output tool that references this path is modified so the original path, i.e. "c:\temp\fllename.ext" becomes "_externals\n\fllename.ext". In general you should not include output files as assets when saving to a server, since they get written to a staging directory on the server which is erased after the workflow is finished.
This process can be used for both input and output asset files. It's most useful when you have a Dynamic Input tool that uses a file as a template. The template file will be replaced in the normal course of running the workflow, but it needs to be there or the workflow throws an error when saved. When specifying that the file should be an asset, it's packaged up with the workflow in the "_externals" path and is always available.