Skip to main content
Validation lets you check a pipeline’s configuration in to find out if it will run successfully. When validating a pipeline, checks the pipeline’s entire configuration, including all component properties and connections between components, but doesn’t run the pipeline. This means that you can identify and fix any issues without consuming credits or performing actions on your data. In , you must validate a pipeline before you can run it or sample the output of any components it contains. We recommend validating pipelines and components often to check your changes.
You can still run an invalid pipeline, but all invalid components in the pipeline will fail and the pipeline run will show as Failed in your pipeline run history. Valid upstream components will succeed—as a result, running an invalid pipeline may consume credits or perform actions on your data.

​
Validating a pipeline

To validate a pipeline:
  1. Open the pipeline in .
  2. Click Validate on the canvas.
The results of the validation are shown in two ways in :
  • In a new row in the Task history tab:
    • A green checkmark if validation was successful (i.e. the pipeline configuration is valid)
    • A red warning if validation failed (i.e. the pipeline is invalid because it contains invalid components or connections)
  • On the canvas:
    • A green border with a checkmark icon around valid components
    • A red border with a cross icon around invalid components

​
Fixing validation errors

If validation fails, you can ask to explain why the pipeline configuration is invalid and help you fix it. To do this:
  • Open the Task history tab, then click Ask in the failed validation task’s row.
  • Click an invalid component on the canvas, then click Ask in the Validation failed section at the top of the properties panel.
If available, click the down arrow in the Validation failed section of an invalid component’s properties panel to read a short explanation for why the component is invalid. This option is available if the reason can be explained concisely—otherwise, click Ask to learn more.