Introduction to the After Date Time Check
The After Date Time check asserts that every value in a Date or Timestamp field is strictly later than a chosen cutoff date and time. Use it to enforce a go-live or migration boundary, validate ingestion timestamps against a floor, or catch stale and backfilled rows.
This section is the complete guide to the check. The Deep Dive covers the definition, properties, and full evaluation semantics, explains how anomalies are reported, walks through production examples, and collects best practices; the How-tos are step-by-step tutorials for creating, editing, and deleting a check; the API page documents the payload for programmatic use; and the FAQ answers the most frequent questions.
Next Steps
-
How It Works
The complete reference: definition, field scope, properties, evaluation flow, NULL handling, filter behavior, and coverage.
-
Anomaly Reporting
The anomaly messages the check produces, what the numbers mean, Source Records highlighting, and Custom Anomaly Description.
-
Examples
Three production scenarios with sample data, anomaly messages, and the SQL equivalent of what the check evaluates.
-
Best Practices
Guidelines for choosing the cutoff, normalizing time zones, pairing rules, and keeping the signal clean.
-
Permissions
The team permission each action needs: view, create, edit, archive, restore, and delete.
-
Create a Check
Step-by-step tutorial for creating an After Date Time check on a table or file.
-
Edit a Check
Step-by-step tutorial for changing the cutoff, filter, coverage, or organizational properties.
-
Delete a Check
Step-by-step tutorial for archiving a check and deleting it permanently.
-
Troubleshooting
Common problems with validation, time zones, NULLs, and anomaly reporting, and how to resolve them.
-
API
Payload shape and field notes for creating an After Date Time check programmatically.
-
FAQ
Short answers to questions about NULLs, inclusivity, time zones, and anomaly reporting.