Ruleset-based rules
Ruleset-based rules check the overall integrity of a dataset — not just individual columns. You add them like any other rule: click “Add new rule”, select any column and choose Format, Freshness or Volume from the Ruleset-based group of the condition list. They serve as foundational health indicators.
What are ruleset-based rules?
Unlike column-level rules, ruleset-based rules assess the entire table and ensure it:
Has been updated recently
Contains an expected number of rows
Matches the expected schema structure
Ruleset-based rules (here freshness and volume) in the Rules tab
Freshness
This rule checks whether the table is updated within an expected time window — for example, once every 24 hours.
Helps detect pipeline issues or delays
Alerts you if the table hasn't been updated recently
Set expected update frequency and monitor actual lag
Volume
This rule checks that the table has a valid row count.
Alerts if the table is unexpectedly empty or too large
Can help identify failed loads or duplicates
Define a row count range and view trend over time
Format
This rule verifies that the schema structure of the table hasn’t changed unexpectedly.
Compares the selected columns with the saved schema: missing columns and changed data types, optionally also newly added columns
Triggers issues if schema drift is detected
Detects schema drift that may affect downstream logic
Notes
Ruleset-based rules are added manually and are inactive until you activate them
Once added, these rules are listed in the Rules tab of the ruleset in the group Ruleset-based rules
Learn more: Overview of existing rules, Working with the Rules tab, Rule prediction