Alteryx Server Knowledge Base

This article shows how to enable the Output Preview in the Workflow Results page in Server UI (a.k.a. Gallery) when running workflows or Analytic Apps that are published to Server.

When a Curator makes certain API calls against the Server Workflow API endpoints, they may get a 403 error code because the workflow is in a different subscription from the Curator.

This workflow downloads all workflows from a Server to a local machine using the V1 API endpoint /webapi/admin/v1/workflows and the V3 API Pack, then parses through the XML to search for a specified term (such as tools used, database connections, DSNs, queries, versions, etc.).

When running a Python workflow on the Server, an initialization error occurs (typeerror: init_io_state).

How to migrate workflows between multiple Alteryx Server environments.

Error resolving python plugin for various Connectors when running on the Server/Gallery.

Invalid Username or Password with Server workflow credentials

How to chain workflows together

Configure a workflow to send an email when a workflow errors on the server or with Desktop Automation.

This article outlines the general recommendations and checklists before an Alteryx Server Upgrade to help achieve a smoother upgrade

Usually, this happens when restarting the AlteryxService after a version upgrade: The scheduled workflows all show as Queued, but none are actually Running. The service logs show the following ERROR message multiple times: 500 Server Error Key fields must be a WString: AS_Schedules__ID

With Alteryx 2020.3 Alteryx introduced a feature to share schedules and their results to collections.

Open Workflow From Gallery Window in Designer Immediately Exits

How to disable the AMP engine on Gallery.

Using AlteryxEngineCmd.exe in the After Run event of a workflow to call another workflow returns "error code: 1: The system could not find the environment option that was entered. (203)" if this workflow completes with warnings.

Document 0 is too large for the cluster

When publishing a workflow that contains a MongoDB Input tool, a validation error is thrown. However, the workflow runs successfully once on the gallery.

The lag that occurs when a workflow name populates in the Save Workflow window in Designer causes workflows to get published to gallery with a blank name.

Engine logs are a useful when troubleshooting Engine related issues. They contain the output of messages created when a workflow runs, as well as the time stamps when tools run in a workflow.

This article shares the defect on sorting schedules in Alteryx Gallery - which is currently not possible in the "Schedules" page of Alteryx Gallery

This article shares the defect around using a PDF filename with a hashtag onto the Image Template tool within Alteryx Designer.