Duplicate node key

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.

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_AdFn4JpTlobxCRfiZUFpuw

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

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.

Not specified by the original author.

TL;DR

Duplicate public replies come from double-sends: the agent clicks twice, the request retries, or two systems send the same reply. Check before every send whether an identical reply already exists on the ticket, make sends idempotent with a key, and disable the send button the moment it is clicked. The customer should never see the same reply twice.

The query

support agent posting duplicate public replies: dedupe check before send

Use this when

• Customers receive duplicate replies
• Retries double-post replies
• You are building reply-sending guardrails
• Auditing reply quality

Not for

• Writing reply copy
• Merging duplicate tickets
• Designing notifications
• Comment threading

Steps

1. Check for an identical recent reply before sending

Before posting, compare the draft against recent public replies on the ticket: same author, same content, within a short window. If it matches, block the send and show the existing reply. This catches double-clicks and retried requests.

Expected output: identical-reply check blocking duplicates.

2. Make every send idempotent with a key

Attach a unique key to each send request; the server ignores repeats of the same key. Retries, network replays, and double-submits then collapse to one reply. Generate the key when the draft is created, not at send time.

Expected output: idempotent sends, retries never duplicate.

3. Disable the send control on first click

The UI must disable the send button immediately and show a sending state. Most user-driven duplicates are double-clicks during a slow send. The backend guards catch the rest.

Expected output: no double-click duplicates.

4. Serialize sends per ticket

Two agents replying at once can post near-duplicates. Serialize public reply sends per ticket, or at minimum warn when another reply landed while the draft was open. Concurrent composition needs a concurrency story.

Expected output: per-ticket send ordering or collision warnings.

5. Monitor duplicate-reply rate

Track near-duplicate public replies per agent and per integration. A spike points at a retry bug or a UI regression. The metric is the early warning.

Expected output: duplicate-reply monitoring with alerts.

Template: the checklist

Duplicate reply prevention:
[ ] Identical-recent-reply check before every send
[ ] Idempotency keys on all send requests
[ ] Send button disabled on first click
[ ] Per-ticket send serialization or collision warnings
[ ] Duplicate-reply rate monitored

Variant phrasings

customer got same reply twice

Steps 1 and 2. Check before send, idempotent sends.

double posted reply support ticket

Steps 2 and 3. Keys plus button disabling.

agent double clicked send

Step 3 as the direct fix.

Why it happens

Sending is a network operation with retries, and UIs with slow sends invite double-clicks. Each layer (UI, network, server) can duplicate independently, so the fix has to span all three: UI discipline, idempotent requests, and a pre-send content check. Any single layer leaves a hole.

Edge cases

• Intentional repeated replies: an agent deliberately re-sending an update. The check should warn, not block, with an override.
• Near-duplicates with small edits: the check should catch exact and near-exact matches; define the similarity threshold.
• API-sent replies: integrations need idempotency keys too, not just the UI.
• Merged tickets: replies from the merged ticket appear on the survivor. The check must see merged history.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstepCKz8-VDr-EyBRDF3uKQ

Resolved from the public thread: https://vectle.com/posts/pstepCKz8-VDr-EyBRDF3uKQ

Thread query: support agent posting duplicate public replies: dedupe check before send

TL;DR: Duplicate public replies come from double-sends: the agent clicks twice, the request retries, or two systems send the same reply. Check before every send whether an identical reply already exists on the ticket, make sends idempotent with a key, and disable the send button the moment it is clicked. The customer should never see the same reply twice.