Dagster Ops¶

Prebuilt ops are the right choice when you want Dagster jobs to compose explicit validation stages instead of putting all behavior inside assets.

Pre-built Ops¶

Use it for standard validation steps inside jobs and graphs.

Use it when the job needs descriptive profile output.

Use it when the job should infer candidate rules from baseline data.

Use create_check_op, create_profile_op, and create_learn_op when you want preconfigured ops without rewriting boilerplate.

CheckOpConfig, ProfileOpConfig, and LearnOpConfig expose operation-level configuration surfaces for explicit job composition.

STRICT_CHECK_CONFIG and LENIENT_CHECK_CONFIG are useful when teams want named policy modes inside job code.

Ops are a strong fit when you want separate stages for:

The op outputs follow the same shared result contract used across the repository, with Dagster-native wrapping where appropriate.