How To: Start the Alteryx Service
The Alteryx Service powers the scheduling functionality of Alteryx. In order for schedules to be created or executed, the Alteryx Service must be running. Follow the guide below for different ways to start the Alteryx Service
Scheduler add-on required
Procedure A - Start from the Services Window
Open the Services snap-in window using one of the below methods:
Search Services in the Start Menu
Press the Windows+R keys to open the Run dialog, type services.msc, and press Enter
Open the Control Panel click/tap on the Administrative Tools icon, and double click/tap on Services shortcut
Right click on Alteryx Service and click Start
Procedure B - Start via System Settings
Open the Alteryx System Settings (can be found in the Start Menu by search "Alteryx System Settings"
Click the Next button until you reach the end of the System Settings, then click Finish
You will then see a "Please Wait" message that indicated the Service is attempting to start
Please note that if the service fails to start for any reason, you will not receive any message to indicate the failure when starting the service this way
Procedure C - Start via Command Line
Open Command Prompt as an Administrator
Type the following command that references your installation path. The below example is the default installation path: "C:\Program Files\Alteryx\bin\AlteryxService.exe" start
Alteryx Service will not start: No suitable servers Error found in LastStartupError.txt
Gallery Service failed to start in a timely fashion
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.
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.
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.