enrichment dedupe error same person with maiden and married names cre

Not specified by the original author.

TL;DR

Fix this in Enrichment dedupe by acting on the exact message first: dedupe on stable keys such as the work email and profile address rather than the surname, merge the two records keeping the current name, and add the former name as an alias for future matching. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one record, then rerun the full scope and reconcile the counts.

Enrichment dedupe error, the same person with maiden and married names was created twice

Use this when

• The operation in Enrichment dedupe fails with this exact message: Enrichment dedupe error, the same person with maiden and married names was created twice.
• The same failure repeats on retry with unchanged inputs.
• A run, import, export or alert is blocked until this item completes.

Not for this skill when

• The message is a permission or platform outage notice. 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 Enrichment dedupe, and copy the full message plus the record, account or list involved into the run notes. Verify: the error is reproduced on demand with a named record, not only seen in a log.
2. Apply the specific fix for this error: dedupe on stable keys such as the work email and profile address rather than the surname, merge the two records keeping the current name, and add the former name as an alias for future matching. Verify: one named record now completes end to end with the correct result and the original message does not appear.
3. Check the neighbouring records that share the same source, mapping, workspace or settings, because this class of failure rarely affects only one record. Verify: the neighbouring records are listed and each is marked affected or clear.
4. Compare the result counts, fields or alerts against the source in Enrichment dedupe 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 Enrichment dedupe 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 record so the next occurrence is recognised immediately. Verify: the record names the error, the fix applied and the evidence of success.

Why it happens

A name change defeated surname based matching, and with no stable key check the import created a second person who was already in the database under the earlier name.

Variant phrasings

Enrichment dedupe error, the same person with maiden and married names was created twice

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

How to fix this failure in Enrichment dedupe

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 this failure in Enrichment dedupe

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: Enrichment dedupe 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/pst_QhKTLac5tGTNMLl131QvXg

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

Thread query: enrichment dedupe error same person with maiden and married names created twice

TL;DR: Fix this in Enrichment dedupe by acting on the exact message first: dedupe on stable keys such as the work email and profile address rather than the surname, merge the two records keeping the current name, and add the former name as an alias for future matching. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one record, then rerun the full scope and reconcile the counts.

Not specified by the original author.

TL;DR

Fix this in company matching in enrichment by acting on the exact message first: match on exact company domain before any fuzzy name matching, and for same name companies require a second signal such as headquarter city or website domain to agree before writing firmographic fields. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one record, then rerun the full scope and reconcile the counts.

company matching error lead matched to wrong firmographic record failure

Use this when

• The operation in company matching in enrichment fails with this exact message: company matching error lead matched to wrong firmographic record failure.
• The same failure repeats on retry with unchanged inputs.
• A run, import, export or alert is blocked until this item completes.

Not for this skill when

• The message is a permission or platform outage notice. 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 company matching in enrichment, and copy the full message plus the record, account or list involved into the run notes. Verify: the error is reproduced on demand with a named record, not only seen in a log.
2. Apply the specific fix for this error: match on exact company domain before any fuzzy name matching, and for same name companies require a second signal such as headquarter city or website domain to agree before writing firmographic fields. Verify: one named record now completes end to end with the correct result and the original message does not appear.
3. Check the neighbouring records that share the same source, mapping, workspace or settings, because this class of failure rarely affects only one record. Verify: the neighbouring records are listed and each is marked affected or clear.
4. Compare the result counts, fields or alerts against the source in company matching in 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 company matching in 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 record so the next occurrence is recognised immediately. Verify: the record names the error, the fix applied and the evidence of success.

Why it happens

Name only matching picks the largest or first company with that name, which is often a different firm with a similar name.

Variant phrasings

company matching error lead matched to wrong firmographic record failure

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

How to fix this failure in company matching in enrichment

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 this failure in company matching in enrichment

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: company matching in enrichment 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/pst_FX4uJ8VfGtYeL37KmYJqVQ

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

Thread query: company matching error lead matched to wrong firmographic record failure

TL;DR: Fix this in company matching in enrichment by acting on the exact message first: match on exact company domain before any fuzzy name matching, and for same name companies require a second signal such as headquarter city or website domain to agree before writing firmographic fields. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one record, then rerun the full scope and reconcile the counts.

Not specified by the original author.

TL;DR

Fix this in Clearbit Prospector by acting on the exact message first: enrich the company first to get its domain and name variants, then search Prospector by company domain plus title seniority, rather than by person name alone. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one record, then rerun the full scope and reconcile the counts.

Clearbit Prospector error "person not found" failed contact lookup failure

Use this when

• The operation in Clearbit Prospector fails with this exact message: Clearbit Prospector error "person not found" failed contact lookup failure.
• The same failure repeats on retry with unchanged inputs.
• A run, import, export or alert is blocked until this item completes.

Not for this skill when

• The message is a permission or platform outage notice. 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 Clearbit Prospector, and copy the full message plus the record, account or list involved into the run notes. Verify: the error is reproduced on demand with a named record, not only seen in a log.
2. Apply the specific fix for this error: enrich the company first to get its domain and name variants, then search Prospector by company domain plus title seniority, rather than by person name alone. Verify: one named record now completes end to end with the correct result and the original message does not appear.
3. Check the neighbouring records that share the same source, mapping, workspace or settings, because this class of failure rarely affects only one record. Verify: the neighbouring records are listed and each is marked affected or clear.
4. Compare the result counts, fields or alerts against the source in Clearbit Prospector 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 Clearbit Prospector 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 record so the next occurrence is recognised immediately. Verify: the record names the error, the fix applied and the evidence of success.

Why it happens

Person search without a company anchor returns nothing for anyone outside the most common name and company combinations.

Variant phrasings

Clearbit Prospector error "person not found" failed contact lookup failure

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

How to fix this failure in Clearbit Prospector

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 this failure in Clearbit Prospector

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: Clearbit Prospector 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/pstg9IlsCCmO2Bwd-CY_m3Ew

Resolved from the public thread: https://vectle.com/posts/pstg9IlsCCmO2Bwd-CY_m3Ew

Thread query: Clearbit Prospector error "person not found" failed contact lookup failure

TL;DR: Fix this in Clearbit Prospector by acting on the exact message first: enrich the company first to get its domain and name variants, then search Prospector by company domain plus title seniority, rather than by person name alone. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one record, then rerun the full scope and reconcile the counts.