Historical Match Ambiguity

A temporal join finds more than one valid historical match.

Temporal joins usually assume that one record on the left side matches exactly one record on the right side.

In practice, overlapping histories, duplicated source records or competing timelines can create multiple valid matches. The join becomes ambiguous because more than one historical record satisfies the join conditions.

A mutation on May 15 matches two customer history records.

Try this Historical Match Ambiguity case in Target Table Validation

Use these sample target tables to test the validator:

1. Copy one of the target tables below.
2. Open Target Table Validation.
3. Paste the copied table as your target output.
4. Check whether the ambiguous match is resolved or still unresolved.

event_id,contract_id,customer_key,event_date,matched_customer_version,valid_from,valid_to,match_status,selection_method
M-1001,C-1001,Customer A,2024-05-15,customer_version_b,2024-04-01,2024-12-31,resolved,deterministic_tie_breaker

event_id,contract_id,customer_key,event_date,matched_customer_version,valid_from,valid_to,match_status,selection_method
M-1001,C-1001,Customer A,2024-05-15,customer_version_a,2024-01-01,2024-06-30,multiple_matches,no_tie_breaker
M-1001,C-1001,Customer A,2024-05-15,customer_version_b,2024-04-01,2024-12-31,multiple_matches,no_tie_breaker

Ambiguity usually appears when histories are aligned.

Each source table can look reasonable on its own. The ambiguity only becomes visible when a temporal join produces more than one candidate record for the same point in time.

Make the intended temporal cardinality explicit.

Count matches before trusting the joined output.

The Workbench can surface ambiguous temporal joins as validation findings.

Match ambiguity is a common source of duplicate facts and unstable KPIs.

Historical Match Ambiguity is often hidden because every individual source table appears valid on its own.

The problem only becomes visible when histories are aligned and multiple candidate matches appear. This can create unexpected reporting growth, duplicated measures and unstable KPI calculations.