Shape · Data quality and flow control

Wait For

Holds a branch back until other steps have finished, then passes its data on. For example, send a Slack message only once the database write is done.

Also known as: Run after, block until done

How it works

The node has no settings. Its upper handle takes the data it passes on unchanged; the lower after handle takes one or more wires from the steps that must finish first: a sink's done handle (Write to DB, Slack, Email) or any node's normal output. The Waits for list in the Attributes panel shows what is wired. Nothing flows through after, and previewing the node does not run those steps; only a full run does. If a waited-on step fails, the Wait For and everything after it are skipped.

Inputs and outputs

Settings

{
}

Example

Send a Slack message once the database write is done: wire the summary table into the data input, the Write to DB node's done handle into after, and a Slack node after the Wait For.

More in Data quality and flow control

• Assert — Checks the data against rules, such as no blanks, unique keys, allowed values or freshness, and stops the run if one fails. Data that passes flows through unchanged.
• Expectations — Runs a set of quality rules and outputs a scorecard with one row per rule, its failed count and pass rate. Unlike Assert, it never stops the run.
• Gate — Passes data on only when a condition holds. The condition can test the data itself, a separate control table or a parameter. Otherwise everything after it is skipped and the run still succeeds. For example, publish only if the extract has rows.
• Compare Tables — Lines up two versions of a table by key columns and puts each value side by side, flagging every cell that changed. A row on only one side shows blanks for the other.