New Pipeline

Pick the Validation Rules that run as Phase 6. Failing rows are quarantined; the Job that produced them then waits for reviewer sign-off in Job Approval (R1 default: requires_approval_on_quarantine).

Cancel Save draft
1 Basics 2 Source & Mapping 3 Transform Chain
4 Validation
5 Schedule & Alerts 6 Review & create

Step 4 · Validation Rules

Rules run against population, the indicator's default_boundary_view, after the built-in Boundary Reconciliation phase. Rules quarantine rows; they do not transform.

#RuleSeverityConfig
1NotNull Remove
2NonNegative Remove
3YearOnYearSwing
max ± % YoY
Remove
4CompletenessPerCountry
expected munis · tolerance
Remove
+ Add a Validation Rule pick from the catalogue ↓
RangeCheck Quarantines rows whose value falls outside [min, max]. UniqueCells No duplicate (muncode, year, sex, age_group) tuples. RegisterCoverage Every output row must reference a known muncode in the active Municipality List. CrossIndicatorCheck Compare with another indicator (e.g. employment ≤ population). NullPercentage Fail when more than X% of rows are NULL. RegexMatch String column must match a regex (rare; mostly for code fields).

Failure behaviour

← Back Continue → Schedule & Alerts

What happens on failure

  • Phase 6 detects failure
    e.g. YearOnYearSwing +22%
  • Row quarantined
    written to validation_queue_rows
  • Job enters Pending Approval
    subscribers + superusers notified
  • Reviewer Approves / Rejects Job
    in Job Approval — Job-level decision
  • "Approve with exceptions" (rare drill-in)
    per-cell Override edit if a single cell needs correction

Will this rule set pass?

Dry-run against last successful job (yesterday 06:01).

Rows tested
11,486
NotNull
● 0 failures
NonNegative
● 0 failures
YearOnYearSwing
● 4 failures · would quarantine
CompletenessPerCountry
● pass · 290/290 munis