Workflow Dependency

Question

Dependency paths within workflows are displaying as "external" instead of the expected absolute path. This occurs when:

* Checking process logs in Alteryx Servers.
* Opening workflows in Designer using "Workflow Dependencies"

We've attempted to fix the issue by:

* Updating workflow dependencies within Designer
* Re-uploading the workflow to the server

Unfortunately, the problem persists after each attempt.

Error.png

alexnajm · Accepted Answer

When you upload the workflow to Server, you need to make sure all network paths are unchecked to prevent them from being changed the "external"

Raj · Accepted Answer

@sourav18 
the reason behind this is because you are packing the sources while saving the workflow on server
while saving the workflow 
click on workflow dependency and uncheck the data sources you did not want to zip in.
this should solve the issue.

sourav18 · Accepted Answer

Thanks for your insight..