Pipeline SQL statements execute sequentially in file order. Each statement completes before the next begins. FAIL_FAST controls whether execution stops on error.
-- Statements execute sequentially top-to-bottomThis reference topic explains how DeltaForge determines the execution order of SQL statements within a pipeline file. Statements are executed sequentially from top to bottom in the exact order they appear in the source file, with each statement completing (or failing) before the next one begins. The `PIPELINE` declaration block itself is metadata and is not executed as a query; only the SQL statements that follow the declaration semicolon are dispatched to the compute node. When the `FAIL_FAST` clause is set to `true` (or simply present without a value, which defaults to `true`), execution halts immediately on the first statement that returns an error, and all subsequent statements are skipped. When `FAIL_FAST` is set to `false`, the pipeline continues executing remaining statements even after a failure, collecting all errors into the run result. If `FAIL_FAST` is omitted entirely from the `PIPELINE` declaration, the default behavior is to stop on the first error, matching `FAIL_FAST true`.