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.
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
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.
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 outlines the issue of missing custom python packages like - Selenium, openpyxl, shareplum, requests_ntlm, etc. after upgrading Alteryx Server/Designer, and the steps to resolve this.
The following error is thrown when attempting to publish workflows to the gallery:
Tool - 1: Unable to create temp directory lock file: "D:ProgramData\Alteryx\Service\Staging\....\__StageTemp\Engine....~.lock". Error: Access is denied. (5)