sqb check

Runs Python checks in isolation. Checks validate the output of tasks, assets, and loaders. For SQL relation validation, use sqb audit instead.

Usage

sqb check [SELECTOR ...] [flags]

Positional SELECTOR arguments work like --select, and both forms can be combined. --project-dir <path>, --no-color, and --debug can go before or after the command name.

Flags

Flag	Description
SELECTOR ...	Positional selectors, the same as --select
--select, -s	Select checks to run (by name, check:, tag:, or graph expansion)
--exclude	Exclude checks from the selection
--no-sql-analysis	Disable compile-time SQL analysis (--no-sql-validation is an alias)
--json	Print check results as JSON
--json-output	Write check results JSON to a file path
--vars	Override project variables
--warehouse <name>	Snowflake warehouse for this invocation; overrides the target’s build warehouse group and the connection warehouse

Selecting a non-check node is rejected; use sqb build to run tasks and assets.

Examples

# Run all checks
sqb check

# Run one check and its required dependencies
sqb check +check_orders_exported

# Run checks by tag
sqb check tag:exports

# Print results as JSON
sqb check --json

Output

Checks report PASS, FAIL, or WARN per check. A failing error-severity check exits non-zero; warn-severity failures are reported without failing the command.

Results are written to target/run/checks/python_checks.json.

Relationship to build

sqb build runs relevant Python checks by default after the tasks, assets, loaders, models, sources, and seeds they depend on have run. sqb build --no-audits skips checks alongside audits. sqb check runs only checks, on demand.