Multiple outputs
A workflow can have as many Output tools as you like, on any branch. A common shape is: main result to a database, exceptions to an Excel file for someone to review, and a summary to a CSV.
That exceptions output is worth building as a habit — rows that failed a join or a validation should go somewhere a person will see them, not be silently dropped.
Splitting into separate files
In the Output tool, set the file path to include a field name in the format Region.csv and tick Take File/Table Name From Field.
One run then produces one file per region. Useful for distributing regional reports without building a workflow per region.
Writing to Excel sheets
Point the output at report.xlsx|||SheetName. Several Output tools with different sheet names build one multi-sheet workbook.
Mind the overwrite setting — Overwrite file removes the other sheets, so use Overwrite sheet when building a workbook from several outputs.
Running unattended
| Option | Notes |
|---|---|
| Alteryx Server / Gallery | Proper scheduling, versioning, permissions |
| Scheduler in Designer | Local, requires the machine to be on |
| Command line | AlteryxEngineCmd.exe workflow.yxmd — driveable from any scheduler |
For anything a business depends on, Server is the answer. A workflow scheduled on someone's laptop is a dependency on that laptop.
Making a workflow rerunnable
Use relative paths, not C:\Users\yourname\.... Set outputs to overwrite or delete-and-append rather than append. Do not rely on a file being deleted by hand between runs.
A workflow that only works the first time is the most common thing handed over and immediately broken.