Historical Coverage Gap
A Historical Coverage Gap occurs when a required historical period has no valid record.
A required reporting period has no valid historical row.
Historical models often assume that every required period is covered by at least one valid record. But in real source systems, histories are often incomplete.
Records may start too late, end too early or contain missing intervals. When reporting depends on a missing period, joins fail, facts lose attributes or snapshots become incomplete.
Customer C1 has history for January to March and May to December, but April is missing.
Any April snapshot or April fact requiring this customer dimension will fail coverage validation or lose dimension attributes.
Try this Historical Coverage Gap case in Target Table Validation
Use these sample target tables to test the validator:
- Copy one of the target tables below.
- Open Target Table Validation.
- Paste the copied table as your target output.
- Check whether the April coverage gap is marked or incorrectly hidden as covered.
Each individual row can look valid while the timeline is incomplete.
Coverage gaps usually appear between otherwise valid records. The problem often only becomes visible when another source, fact table or snapshot date needs that missing period.
Make historical coverage explicit before joining.
Validate coverage against the periods your reports actually need.
The Workbench can surface coverage gaps as validation findings.
Coverage gaps are easy to miss and expensive to debug later.
Historical gaps are easy to miss because each individual record can look valid.
The problem only appears when the model is queried for a missing period or joined against another historical source. Coverage validation makes these gaps visible before they create incorrect reports.
Detect historical coverage gaps in your own model.
Use the Historical Modeling Workbench to validate temporal coverage, detect gaps and understand where historical joins or snapshots can fail.
Open Historical Modeling Workbench →