identity enrichment error duplicate accounts merged wrong user in alert failure

Not specified by the original author.

TL;DR

Fix this in identity enrichment by acting on the exact message first: change the merge key from name similarity to the immutable employee or object ID, unmerge the two accounts that were combined, and add a manual review step when IDs differ but names match closely. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one item, then rerun the full scope and reconcile the counts.

identity enrichment error duplicate accounts merged wrong user in alert

Use this when

• The operation in identity enrichment fails with this exact message: identity enrichment error duplicate accounts merged wrong user in alert.
• The same failure repeats on retry with unchanged inputs.
• A review, export or check is blocked until this item completes.

Not for this skill when

• The message is a permission or outage notice from the platform. Resolve that first, then return here if this error remains.
• The operation completes and you only disagree with its output. That is a quality review, not this failure.

Steps

1. Reproduce the failure with the smallest scope that still shows it in identity enrichment, and copy the full message plus the alert, incident or enrichment record involved into the run notes. Verify: the error is reproduced on demand with a named item, not only seen in a log.
2. Apply the specific fix for this error: change the merge key from name similarity to the immutable employee or object ID, unmerge the two accounts that were combined, and add a manual review step when IDs differ but names match closely. Verify: the two users appear as separate identities and new alerts attach to the correct one.
3. Check the neighbouring items that share the same config, template, feed or credential, because this class of failure rarely affects only one item. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Compare the result counts, decisions or alerts against the source in identity enrichment so a silent partial success is caught before sign off. Verify: counts match the source or every difference is named and explained.
5. Rerun the original operation in identity enrichment on the previously failing scope, watching for the same message rather than assuming success from a quiet log. Verify: the operation completes and the original message does not appear.
6. Record the fix, the triggering input and the verification result on the item so the next occurrence is recognised immediately. Verify: the record names the error, the fix applied and the evidence of success.

Why it happens

fuzzy matching on similar names merged two different people into one identity, and every later alert inherited the wrong person context.

Variant phrasings

identity enrichment error duplicate accounts merged wrong user in alert

The verbatim form searchers paste from the terminal or console. Treat it identically: same fix, same single item proof, then the full rerun.

How to fix: identity enrichment error duplicate accounts merged wrong user in alert failure

The how-to phrasing for the same failure in identity enrichment. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.

identity enrichment troubleshooting for this failure

The symptom-first phrasing used when the console hides the full message. Surface the full message first, confirm it matches the code block above, then follow the steps.

Compatibility: identity enrichment at current versions, plus the platform API or console the query names; no extra tooling beyond a text editor and the source system access needed to verify counts.

Provenance

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

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

Thread query: identity enrichment error duplicate accounts merged wrong user in alert failure

TL;DR: Fix this in identity enrichment by acting on the exact message first: change the merge key from name similarity to the immutable employee or object ID, unmerge the two accounts that were combined, and add a manual review step when IDs differ but names match closely. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one item, then rerun the full scope and reconcile the counts.

Not specified by the original author.

TL;DR

Fix this in DSR identity resolution by doing this first: unmerge the profiles back to their source records, rebuild the match on strong identifiers only, re-run the export for the correct person alone, and treat the earlier delivery as an incident with the privacy lead informed. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one item, then rerun the full scope and reconcile the counts.

two profiles merged with wrong person export

Use this when

• The operation fails with this exact problem: two profiles merged with wrong person export.
• The same failure repeats on retry with unchanged inputs.
• An audit, review, or request is blocked until this item completes.

Not for this skill when

• The message is a platform outage notice or a general sign-in failure. Resolve that first, then return here if this problem remains.
• The operation completes and you only disagree with its output. That is a quality review, not this failure.

Steps

1. Reproduce the failure with the smallest scope that still shows it in DSR identity resolution, and copy the full message plus the item, account, or request involved into the run notes. Verify: the problem is reproduced on demand with a named item, not only seen in an old log.
2. Apply the specific fix for this problem: unmerge the profiles back to their source records, rebuild the match on strong identifiers only, re-run the export for the correct person alone, and treat the earlier delivery as an incident with the privacy lead informed. Verify: the single test item now completes or shows the expected state on a direct read-back from the source.
3. Check the neighbouring items that share the same connection, mapping, owner, or credential, because this class of failure rarely affects only one item. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Compare the result counts, decisions, or statuses against the source system so a silent partial success is caught before sign-off. Verify: counts match the source or every difference is named and explained.
5. Rerun the original operation on the previously failing scope, watching for the same problem rather than assuming success from a quiet log. Verify: the operation completes and the original problem does not appear.
6. Record the fix, the triggering input, and the verification result on the item so the next occurrence is recognised immediately. Verify: the record names the problem, the fix applied, and the evidence of success.

Why it happens

A weak match on a shared attribute merged two people, so the export mixed another person details into this requester package, which is both a wrong fulfilment and a disclosure risk.

Variant phrasings

how to fix DSR duplicate identity error two profiles merged wrong person export fails

The verbatim form searchers paste from the console or ticket. Treat it identically: same fix, same single item proof, then the full rerun.

How to fix this failure in practice

The how-to phrasing for the same failure. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.

Troubleshooting the symptom-first form

The phrasing used when the console hides the full message. Surface the full message first, confirm it matches the code block above, then follow the steps.

Compatibility: OneTrust, Transcend, DataGrail, and Securiti class privacy platforms at current versions, plus the source systems the query names; no extra tooling beyond the platform console or API access needed to verify counts.

Provenance

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

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

Thread query: how to fix DSR duplicate identity error two profiles merged wrong person export fails

TL;DR: Fix this in DSR identity resolution by doing this first: unmerge the profiles back to their source records, rebuild the match on strong identifiers only, re-run the export for the correct person alone, and treat the earlier delivery as an incident with the privacy lead informed. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one item, then rerun the full scope and reconcile the counts.

Not specified by the original author.

TL;DR

Fix this in customer health score by acting on the exact message first: after the CRM merge, repoint the health inputs to the surviving account record, merge the usage and ticket history from the retired duplicate instead of discarding it, clear any score cached against the retired record id, and recalculate the survivor from the combined history. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one account, batch or record set first, then rerun the full scope and reconcile the counts.

customer health score wrong after duplicate accounts merged in CRM

Use this when

• The operation in customer health score fails with this exact message or symptom: customer health score wrong after duplicate accounts merged in CRM.
• The same failure repeats on retry with unchanged inputs.
• Scoring, alerting or routing is blocked until this item completes.

Not for this skill when

• The message is an outage notice from the platform. Resolve that first, then return here if this error remains.
• The operation completes and you only disagree with its output quality. That is a quality review, not this failure.

Steps

1. Reproduce the failure with the smallest scope that still shows it in customer health score, and copy the full message plus the account, measure or job involved into the run notes. Verify: the error is reproduced on demand with a named scope, not only seen in a log.
2. Apply the specific fix for this error: after the CRM merge, repoint the health inputs to the surviving account record, merge the usage and ticket history from the retired duplicate instead of discarding it, clear any score cached against the retired record id, and recalculate the survivor from the combined history. Verify: the smallest failing scope now completes, or the named account, measure or job behaves as the fix predicts.
3. Check the neighbouring accounts, measures or jobs that share the same config, schema or credential, because this class of failure rarely affects only one item. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Rerun the original operation in customer health score on the previously failing scope, watching for the same message rather than assuming success from a quiet log. Verify: the operation completes and the original message does not appear.
5. Compare the result counts, scores or status against the source in customer health score so a silent partial success is caught before sign off. Verify: counts match the source or every difference is named and explained.
6. Record the fix, the triggering input and the verification result on the item so the next occurrence is recognised immediately. Verify: the record names the error, the fix applied and the evidence of success.

Why it happens

The score keeps reading whichever record id it was bound to, and a merge that retires that id or drops its history leaves the survivor scored from a partial or empty past.

Variant phrasings

customer health score wrong after duplicate accounts merged in CRM

The verbatim form searchers paste from the terminal or console. Treat it identically: same fix, same single scope proof, then the full rerun.

How to fix - customer health score wrong after duplicate accounts merged in CRM error failure

The how-to phrasing for the same failure in customer health score. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.

customer health score troubleshooting for this failure

The symptom-first phrasing used when the console hides the full message. Surface the full message first, confirm it matches the code block above, then follow the steps.

Edge cases

• If the fix works on the sample scope but the full rerun still fails, a second account or record with the same fault is present; widen the scope in stages until the next failing item is found.
• If scores change after the fix but downstream alerts or reports do not, check the downstream refresh timing before recalculating again, because those surfaces often read a synced copy.
• If the source data itself is missing for the affected accounts, record that as a data gap rather than scoring the accounts as zero.

Compatibility: customer health score at current versions, plus the platform API or console the query names; no extra tooling beyond the source system access needed to verify counts.

Provenance

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

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

Thread query: customer health score wrong after duplicate accounts merged in CRM error failure

TL;DR: Fix this in customer health score by acting on the exact message first: after the CRM merge, repoint the health inputs to the surviving account record, merge the usage and ticket history from the retired duplicate instead of discarding it, clear any score cached against the retired record id, and recalculate the survivor from the combined history. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one account, batch or record set first, then rerun the full scope and reconcile the counts.