Introduction to the Issue

Parsing workflows is vital for WAM Server to perform basic functions, from Search/Update to Migrating workflows. Parsing a workflow means that the workflow package is being downloaded from the Alteryx Gallery and stored in the "Gallery Workflows" folder located in your configured WAM Output folder mapped in the Settings menu. If you are having trouble parsing workflows in WAM Server, this article is for you. It is likely that the workflow(s) selected may have their download access disabled. In the first part of this article, we will be talking about how to find which workflows have and have not been parsed and how to determine which workflows cannot be downloaded. Once we have determined which workflows are parsed and whether they are able to be downloaded or not, we will then look into why the workflows cannot be downloaded. Lastly, we will talk about how to enable workflow downloads in bulk using WAM Server.

Finding Workflow Parsed and Download Status in WAM Server

To find the current parse status of workflows in the Gallery that we are connected to, click the "Filters" button, and in the prompts, change the Columns to "Parsed" and Status to "false". This filter will return all workflows in the Gallery that have not been locally parsed. The screenshot below is what the filter would look like applied to your Gallery workflows. The number at the bottom, highlighted in red, shows the number of workflows that match the filter criteria compared to the entire list of workflows.

Once we have determined the workflows that are not parsed, we should check their downloadable status. We will add another filter (shown below) to determine which workflows are not parsed and are not downloadable. If any workflows meet this criterion, the workflows will appear in the workflow viewer, as shown in the screenshot below.

Finding Workflow Parsed 

Parsing the workflow requires the workflow to be downloaded from the Gallery. In the previous section, we determined if the workflows are not parsed and not downloadable. If the workflows are marked as not "downloadable", we can access the workflow in Alteryx Gallery and toggle the ability to enable or disable downloads. The screenshot below shows how to access the Workflow settings and enable downloads for the workflow. Check this box, save the settings, and run an API and Mongo refresh in WAM Server and reparse your workflow. If multiple workflows have their downloads disabled, skim the rest of this section (to ensure the Admin setting is set to False) and move to the next section to learn how to use WAM Server to mass update your workflows to allow downloads.

In the exception that we noted in the previous section, it is possible that the Admin > Asset > Disable Direct Download is set to True. This setting will need to be updated in order for WAM to download and parse your Gallery workflows. Flip this switch, save the settings, and run an API and Mongo refresh in WAM Server and reparse your workflows.

If either or both of the above options are toggled to disable downloads, the options will need to be flipped to allow downloads for WAM to update and migrate workflows. You will need to run an API and Mongo refresh after updating these settings in order for the WAM Server parsing to work.

In the migrations section, you can select “Update Existing” and flip the “Enable Download” switch in the Advanced Options on to reflect the screenshot below. You will need to batch the updates based on workflow ownership. This can be done by adding an additional filter based on "Owner" and setting the value to the owner of at least one of the workflows. For example, in the screenshot below, the 4 workflows I have selected will need to be migrated separately based on the ownership of the workflows. I would only choose the workflows owned by me first, migrate to update the downloadable function, and then move to the next user’s workflows, and so on.