Introduction to the Between Times Check
The Between Times check asserts that every value in a Date or Timestamp field falls inside a start and an end instant. Both boundaries are inclusive. Use it to keep dates inside a reporting period, a contract term, or any other window with a fixed beginning and end.
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, inclusive boundaries, 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 window, handling 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 a Between Times check with a start and an end instant.
-
Edit a Check
Step-by-step tutorial for moving either boundary, or changing the filter, coverage, or organizational properties.
-
Delete a Check
Step-by-step tutorial for archiving a check and deleting it permanently.
-
Troubleshooting
Common problems with inclusive boundaries, time zones, NULLs, and anomaly reporting, and how to resolve them.
-
API
Payload shape and field notes for creating a Between Times check programmatically.
-
FAQ
Short answers to questions about the window, inclusivity, time zones, and anomaly reporting.