Ben Stringer

Ben Stringer

Technical Consultant at Bulien

Roan Pilsworth

Roan Pilsworth

Technical Consultant at Bulien

You have moved a workflow to Alteryx One, you want it to run every morning, and the schedule option is nowhere to be found. Or it is there, and you are not sure whether to use a fixed time, cron, an event trigger or Orchestrator.

Most of that is settled earlier than people expect. Whether a workflow can be scheduled at all depends on how it was uploaded. And once workflows depend on each other, the right thing to schedule is a plan, not the individual workflows.

Upload the package, not the bare workflow

When you save from Designer Desktop to Alteryx One, you choose between uploading the workflow on its own (a .yxmd) or as a zip package. The bare workflow goes up without its source data. The package includes assets such as macros and input files.

In our demonstration, Ben Stringer found that a workflow uploaded on its own showed no scheduling option at all, while the package did. That makes sense, since a workflow with no data has nothing to run against. His advice was to always pick the package for now, and we agree. If scheduling seems to be missing, check this first.

Schedule from the library

The route that worked reliably on camera was the library.

  1. In Designer Desktop, choose File, Save As, Alteryx One.
  2. Name the workflow, pick the folder, choose the zip package option and tick the input files to include.
  3. In Alteryx One, find the workflow in your library (the upload time confirms it is the right one).
  4. Click the triple dots on the workflow package and choose New schedule.
  5. Name the schedule, choose the frequency and time, and save.
  6. Check Schedules for the next run, then Jobs to confirm it ran.

You might expect to start from the Schedules pane instead. When Ben tried it, the asset dropdown would not list his Designer workflow, which he took to be something Alteryx still needed to add.

The finished job’s output downloads as a zip containing your output file and the engine log, which is worth reading after the first run.

Pick the simplest frequency that does the job

At the time of recording the options were hourly, daily (with a working-week option), weekly, monthly, once, custom and event trigger. Custom uses cron, for patterns like the third Friday of each month, and the Learn More link explains how to read it.

Ben’s preference is recurring or once for most jobs, with custom kept for when you really need it. We agree, because the next person to maintain the schedule should be able to read it at a glance.

Use event triggers where the timing is unpredictable, and test them

An event trigger runs the schedule when something changes, which suits data that lands at unpredictable times.

Ben showed a trigger on a Snowflake table. It fires on table modification, so a row inserted, updated or deleted sets the schedule off. Create the connection first, under Data, then Create Connection: starting it from inside a schedule took him away with no back button.

The second kind watches one named file in Alteryx data storage (not a folder, as Ben understood it) on a five minute polling rate, and runs when someone replaces the file. He could not get it to fire during the recording, so test it before anything depends on it.

When workflows depend on each other, schedule a plan

A schedule runs one asset. If workflow B should only run after workflow A succeeds, two schedules with a gap between them is fragile. Use Orchestrator.

You build a plan on a canvas from tasks such as Designer Cloud and Designer Desktop workflows, Live Query and Auto Insights dataset refreshes, plus email, Slack, HTTP request, delay and approval steps. Each task has on success, on failure and always anchors, so a plan can run the next step only if the last one worked, or send an alert if it failed. Roan Pilsworth called it a step up from macros, because a macro has to live entirely in Designer.

The approval step is the one we would use most in finance and HR reporting. It pauses the plan and emails the people you choose, with one or all responses required and a time limit so it does not hang forever. The plan’s “running for” timer keeps counting while it waits, so a long run time may only mean a slow approver.

What to expect once a plan is running

Scheduling a plan works like scheduling a workflow, plus email notifications for all runs (the default), failed runs or successful runs. We would usually pick failures only.

Each run is kept as a snapshot showing the failing tool and the error. Retry from failed reruns only the tasks that did not succeed, and Ben confirmed in Jobs that the workflow that had already worked was not run again. His complaints: no searchable list of runs to filter down to failures, and no parent view of the plan in Jobs.

Plans can be shared as viewer, contributor or editor, and Ben found the underlying workflows stayed view only for the person he shared with. They can be exported as a zip containing JSON and imported elsewhere, say from development to production, though run history does not come across.

Ben notes that the options depend on your Alteryx One edition (Starter, Professional or Enterprise). Alteryx Server scheduling is a separate subject.

See it done

Watch on YouTube

Ben uploads a workflow from Designer Desktop, schedules it and checks the job output.

Moving your schedules to Alteryx One?

We have begun moving a lot of our customers across to Alteryx One. If you want a second pair of eyes on how your workflows are scheduled, or on which of them belong in one plan, read more about our Alteryx work or get in touch.