Alteryx Designer Knowledge Base

Desktop Scheduler does not support the use of Python-based connectors

Here at Alteryx we believe in working smart, not hard. Building out reports to highlight business-critical metrics is a pretty smart way to track goals. Customizing those reports to everyone in the department, then distributing them as attachments to individual emails? That sounds like a lot of hard work. Scheduling those reports from a refreshing data source each month so you don’t have to remake or rerun the reports yourself - that’s genius. Logging into your work computer to open up Alteryx, then having to check the scheduled results before having any peace of mind those reports were delivered without a hitch? Hard.

Error "Unable to find the dll: "AlteryxBasePluginsEngine.dll"" in workflows containing a Python-based Connector and a Table Tool

The article provides the steps to run workflow on a Google Drive from Desktop Automation.

How Alteryx Designer and Server use file paths

An error is thrown when scheduling a workflow in Desktop Scheduler in a non-English language. This only occurs with the 'Custom' option under Frequency.

When publishing a workflow to Gallery or Scheduler (Designer + Desktop Automation) or when packaging a workflow for export, checking the boxes for what to include and what to exclude seems to work inconsistently as of Designer 2020.2. The workaround will tide you over until you can upgrade to 2021.2.

Everything you need to get started with your own instance of Designer + Scheduler!

When running a workflow via the Scheduler (for Designer with Automation), the following error is observed:

Issue: Unable to connect to the Controller "X"

Why did all of my scheduled workflows fail? What does the error “Logon Failure: unknown user name or bad password” mean? Read this article to find out!

This article details the required steps to transfer workflow schedules from one computer to another when using Desktop Scheduler and a SQLite database.

  On Alteryx version 10.1, if you try to schedule a workflow to to run from its original location on disk and the workflow path starts with a digit, for example C:\1testpath\workflow.yxmd, the workflow will fail to run on the Scheduler. When the job fails, you will see the job at the bottom of the Results view within the Scheduler window and the job date is January 01 0001 12:00:00 AM - this indicates a corrupt job. All other combinations work as expected.          This is a known issue that is being addressed. The workaround is to rename the folder so that the path does not start with a digit, for example C:\a1testpath\. Alternatively, you can schedule the job to run a copy of the workflow stored in the scheduler DB. 

What’s the difference between Scheduling a workflow from its original location on disk vs as a copy in the Scheduler DB?

So you've installed the licenses to run Scheduler. Now what?

I know I set this right, but it's not doing what I want it to!

Error: Can’t find the file: “[path\FileName]”. Make sure the file path is correct. Error text being revised from Error: File not found "[path\FileName]"

This article is an extension to the community article "Scheduling as a copy in the Scheduler DB vs On Disk", and is specifically aimed for Designer + Desktop Automation installations only.

This article covers how to use Run Command events to run a workflow.

Upon creating a BINGO game, I came across a technique that I thought could be useful in "real world" scenarios for users who are attempting to iterate a process and then replenishing the data after a certain amount of time.