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.
The AlteryxServerUsageReport.zip available on the Downloads Portal is for versions 2019.3 and below. In versions 2020.1+, Tableau output fails with error “Error: Alteryx Server Usage Report (8): RunBatch (695): Tool #1: The external program ".\CollectionCheck.bat" returned an error code: 1”.
When performing a Server migration, an error may occur when attempting to set the Controller token on the new Server to the value from the original Server through Command Line. The resolution to this issue is to remove the existing "ServerSecretEncrypted" value from the RuntimeSettings.xml file.
An access denied error is thrown when expanding the results of a manual job run by a different user or a scheduled job that has not been shared with that user through a collection.
Any user that needs to schedule a workflow that contains a Python Based Connector needs to reach out to their Account Executive or Sales Engineer to make changes in order for the workflows to be scheduled and run without issues.
This article goes over the symptoms of schedules that are set to run during the hour that is skipped 2 am to 3 am when Standard Time changes to Daylight Savings Time spring forward and the hour that's repeated 1am to 2am when Daylight Savings Time changes back to Standard Time fall back.
This article discusses how a GET "/v1/jobs/{jobId}/" API call may return a "Job Not Found" response when using the Private Studio API keys, and how to change the API call to retrieve the job status.
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.