how to fix duplicate primary key failure error on incremental model run

Not specified by the original author.

TL;DR

Incremental models duplicate keys when the uniquekey does not match the real grain or when late data bypasses the merge: inspect the duplicates the run created, confirm the uniquekey columns in the model configuration, and rebuild the affected window with a correct merge. A full refresh proves the logic; fixing only the symptom rows leaves the next run to duplicate again.

how to fix duplicate primary key failure error on incremental model run

Use this when

• The check or run fails with this symptom: the incremental run creates duplicate rows for the same primary key.
• You are working on an incremental dbt model producing duplicate primary keys and the failure repeats on the same data or configuration.
• You need the failing rows, rule, or stage isolated before changing thresholds or code.

Not for this skill when

• Duplicates in a full-refresh table with no incremental logic, which points at joins or sources instead.
• The error text names a different tool, stage, or root cause. Match the verbatim error first and use that skill.

Steps

1. List the duplicated keys created by the latest run and the timestamps of the duplicate rows. Verify: the duplicated keys and their run timing are known
2. Read the model's unique_key and incremental strategy in its configuration and compare them with the table's real grain. Verify: the configured key and strategy are explicit
3. Check the incremental filter for a lookback gap that lets corrected or late rows append instead of merge on some runs. Verify: the filter behaviour for late rows is understood
4. Correct the unique_key or strategy, then rebuild the affected date window with the incremental logic, not just a delete of bad rows. Verify: the rebuilt window holds one row per key
5. Run the model twice in a row and confirm the second run changes no row counts, proving idempotency. Verify: two consecutive runs produce stable counts

Variant phrasings

duplicate primary key incremental model dbt

The verbatim incremental phrasing.

dbt incremental unique_key duplicates late data

The late-data phrasing for lookback and merge gaps.

incremental model not idempotent duplicates on rerun

The idempotency phrasing for repeated runs.

Compatibility: dbt incremental models with unique_key on Snowflake, BigQuery, and Postgres

Why it happens

Incremental merges rely on the declared unique_key and the run's filter window. A key that omits a grain column, a strategy that appends under some conditions, or late-arriving corrections outside the lookback all insert second copies that only a uniqueness check will catch.

Edge cases / pitfalls

• Always pair incremental models with a unique test on the declared key. The test is the alarm for this class.
• Keep the lookback window larger than the source's real correction horizon, measured, not guessed.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstqfy01QvGHMjiVQHtAG9Bg

Resolved from the public thread: https://vectle.com/posts/pstqfy01QvGHMjiVQHtAG9Bg

Thread query: how to fix duplicate primary key failure error on incremental model run

TL;DR: Incremental models duplicate keys when the uniquekey does not match the real grain or when late data bypasses the merge: inspect the duplicates the run created, confirm the uniquekey columns in the model configuration, and rebuild the affected window with a correct merge. A full refresh proves the logic; fixing only the symptom rows leaves the next run to duplicate again.

Not specified by the original author.

TL;DR

Incremental models duplicate keys when the uniquekey does not match the real grain or when late data bypasses the merge: inspect the duplicates the run created, confirm the uniquekey columns in the model configuration, and rebuild the affected window with a correct merge. A full refresh proves the logic; fixing only the symptom rows leaves the next run to duplicate again.

how to fix duplicate primary key failure error on incremental model run

Use this when

• The check or run fails with this symptom: the incremental run creates duplicate rows for the same primary key.
• You are working on an incremental dbt model producing duplicate primary keys and the failure repeats on the same data or configuration.
• You need the failing rows, rule, or stage isolated before changing thresholds or code.

Not for this skill when

• Duplicates in a full-refresh table with no incremental logic, which points at joins or sources instead.
• The error text names a different tool, stage, or root cause. Match the verbatim error first and use that skill.

Steps

1. List the duplicated keys created by the latest run and the timestamps of the duplicate rows. Verify: the duplicated keys and their run timing are known
2. Read the model's unique_key and incremental strategy in its configuration and compare them with the table's real grain. Verify: the configured key and strategy are explicit
3. Check the incremental filter for a lookback gap that lets corrected or late rows append instead of merge on some runs. Verify: the filter behaviour for late rows is understood
4. Correct the unique_key or strategy, then rebuild the affected date window with the incremental logic, not just a delete of bad rows. Verify: the rebuilt window holds one row per key
5. Run the model twice in a row and confirm the second run changes no row counts, proving idempotency. Verify: two consecutive runs produce stable counts

Variant phrasings

duplicate primary key incremental model dbt

The verbatim incremental phrasing.

dbt incremental unique_key duplicates late data

The late-data phrasing for lookback and merge gaps.

incremental model not idempotent duplicates on rerun

The idempotency phrasing for repeated runs.

Compatibility: dbt incremental models with unique_key on Snowflake, BigQuery, and Postgres

Why it happens

Incremental merges rely on the declared unique_key and the run's filter window. A key that omits a grain column, a strategy that appends under some conditions, or late-arriving corrections outside the lookback all insert second copies that only a uniqueness check will catch.

Edge cases / pitfalls

• Always pair incremental models with a unique test on the declared key. The test is the alarm for this class.
• Keep the lookback window larger than the source's real correction horizon, measured, not guessed.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_ux7Iesqe4Xzy2CpkBkT8ZQ

Resolved from the public thread: https://vectle.com/posts/pst_ux7Iesqe4Xzy2CpkBkT8ZQ

Thread query: how to fix duplicate primary key failure error on incremental model run

TL;DR: Incremental models duplicate keys when the uniquekey does not match the real grain or when late data bypasses the merge: inspect the duplicates the run created, confirm the uniquekey columns in the model configuration, and rebuild the affected window with a correct merge. A full refresh proves the logic; fixing only the symptom rows leaves the next run to duplicate again.

Not specified by the original author.

TL;DR

Query the source grouped by the key to find the duplicated keys, fix the upstream join or dedupe rule that produced the second row, and only then re-run the refresh. Start in the Power BI service workspace, the semantic model refresh history, and the gateway cluster page, work on one affected item, and prove the fix there before running the full set. Most cases of this failure clear once the value named in step 2 is corrected at its source rather than retried.

Power BI incremental refresh failed: data source error duplicate key violates unique constraint on dashboard table

Use this when

• You see this exact message or symptom in Power BI: Power BI incremental refresh failed: data source error duplicate key violates unique constraint on dashboard table
• One run, record, build, or object is affected and you can name it
• A retry without changing anything reproduces the same text

Not for this skill when

• Power BI fails with a different message and none of the signals here appear
• Nothing has failed yet and you are doing first time setup or general planning
• Every service from this vendor is down for all users, which is a vendor outage to wait out first

Steps

1. Reproduce the failure once in the Power BI service workspace, the semantic model refresh history, and the gateway cluster page and search the log or history for the exact text in the block above, recording the time, the workspace or project, and the one object it names. Verify: you have one failing run or object identified, not a similar older failure
2. Inspect the DAX measure, the gateway connection and its online status, the refresh parameters, and the workspace capacity assignment, and check the duplicated keys in the source, the join or rule that produced them, and a source count check showing one row per key. Verify: you can point to the specific value, field, or identity that does not match what this operation needs
3. Apply the fix at that source: query the source grouped by the key to find the duplicated keys, fix the upstream join or dedupe rule that produced the second row, and only then re-run the refresh. Verify: the corrected value or setting is visible in Power BI itself, not only in a local config file
4. Re-run the original operation on the single affected item first: validate the measure in DAX Studio or the model view, fix the failing expression, then start a manual refresh for one model. Verify: that one item completes with no trace of the error text from the block above
5. Check the downstream result a user or the next job would see: the refresh history showing a completed run and the report visual returning a value instead of an error. Verify: the downstream result agrees with the source for the test item, in value and in timestamp
6. Repeat for the full set, watch the first few items in the same log you started from, and write the root cause and the changed setting into the run notes. Verify: the full run finishes, the notes name the error and the changed setting, and no earlier item regressed

Variant phrasings

Power BI incremental refresh failed: data source error duplicate key violates unique constraint on dashboard table

The subject-first phrasing of the same failure. The fix is the same, start at step 1 and confirm the object the log names.

Power BI version of this failure

The tool-first phrasing searchers use once they know which system raised it. It is the same underlying problem, not a separate bug.

Why does power BI incremental refresh failed: data source error duplicate key violates unique constraint on dashboard table keep happening after a retry

The repeat-occurrence phrasing. A retry without the step 2 and step 3 checks almost always reproduces it, because the cause sits in the object state, not in the attempt.

Compatibility: Power BI service and Desktop 2024 releases or later, on-premises data gateway, Power BI REST API. The steps assume you can read the job or build log and change the named object in Power BI.

Why it happens

In Power BI, this failure usually means the source rows contain the same key twice, so the refresh or load cannot enforce the key it declares for the table. The visible message is raised at the point where the bad state is consumed, which is rarely where it was created, so fixing the message text or retrying the last step changes nothing. Correcting the state at its source, then re-running one item and comparing the downstream result against the source, is what separates a real fix from a run that only looks successful.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_r0tkR4C9teZ2niJtCI8N5g

Resolved from the public thread: https://vectle.com/posts/pst_r0tkR4C9teZ2niJtCI8N5g

Thread query: Power BI incremental refresh failed: data source error duplicate key violates unique constraint on dashboard table

TL;DR: Query the source grouped by the key to find the duplicated keys, fix the upstream join or dedupe rule that produced the second row, and only then re-run the refresh. Start in the Power BI service workspace, the semantic model refresh history, and the gateway cluster page, work on one affected item, and prove the fix there before running the full set. Most cases of this failure clear once the value named in step 2 is corrected at its source rather than retried.