Introduction to the Not Future Check
The Not Future check asserts that a date or timestamp is not ahead of the present moment. It is the rule for fields that record something that already happened, where a future value means a clock, a time zone, or a data-entry mistake rather than a real event.
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, what "now" means, array handling, 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 right field, handling clock skew, and picking between Not Future and a fixed bound.
-
Permissions
The team permission each action needs: view, create, edit, archive, restore, and delete.
-
Create a Check
Step-by-step tutorial for creating a Not Future check on a date or timestamp field.
-
Edit a Check
Step-by-step tutorial for changing the field, the filter, or the coverage on an existing check.
-
Delete a Check
Step-by-step tutorial for archiving a check and deleting it permanently.
-
Troubleshooting
Common problems with time zones, clock skew, arrays, and anomaly reporting.
-
API
Payload shape and field notes for creating a Not Future check programmatically.
-
FAQ
Short answers to questions about the reference moment, NULLs, arrays, and anomaly reporting.