Skip to main content
A pipeline connects inputs, processing steps, and outputs. Use it to repeat imports, data preparation, model training, prediction, or exports. A pipeline definition describes the work. A run is one execution of that definition. Inspect the run that produced a result when investigating errors or changes.

Understand the canvas

Connections between nodes establish the flow of data. Check the configured dataset and model names as well as the visible node labels.

Create a pipeline

Use Create → Pipeline in Workspace, or ask Dawn to create one from a conversation. Attach the relevant datasets and connections first.
Review the generated canvas and each action’s configuration. For manual editing, use the available node controls to add datasets, actions, and model outputs, then connect the required inputs. See data engineering for a preparation walkthrough and modelling for a training workflow.

Choose the right operation

An import and an export require different access. Review the destination and write behaviour before running an export.

Save and run

Use Save before Run. The pipeline also has Code, Info, MLOps, History, and Logs tabs. Open a step to inspect its Configuration and Logs. Use Run this step or Run from this step when you need a smaller rerun, and watch its status. For a subset run, make sure any upstream datasets and models already exist and contain the versions you intend to use. A completed run means the configured steps finished. It does not establish that the business logic is correct. Open the output datasets or models and compare their contents with your expectations.

Troubleshoot a failed run

  1. Open the run history or logs for the failed run.
  2. Find the first failed step; downstream steps may not have run because of it.
  3. Check that step’s configuration, inputs, and error message.
  4. Add the pipeline and relevant error details to a conversation for help.
  5. Review the proposed change, save it, and rerun the appropriate steps.

Schedule recurring work

Open Info and use Schedule to configure recurring runs after a successful manual run and validation of the output. Save the schedule with Save changes. Check its timezone, intended input period, and expected duration. Avoid overlapping runs unless the workflow is designed for them. Use a Job when the recurring work is an instruction to an agent, such as reviewing results and writing commentary. Use an Automation when you need a visual workflow of actions. These are distinct from the data-processing steps in a pipeline.