lead enrichment error personal email enriched as work email failure

Not specified by the original author.

TL;DR

Fix this in personal email handling in enrichment by acting on the exact message first: flag free and personal email domains with a maintained freemail list, keep those leads out of company enrichment, and match them to a company only from an explicit company field on the lead. 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.

lead enrichment error personal email enriched as work email failure

Use this when

• The operation in personal email handling in enrichment fails with this exact message: lead enrichment error personal email enriched as work email 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 personal email handling 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: flag free and personal email domains with a maintained freemail list, keep those leads out of company enrichment, and match them to a company only from an explicit company field on the lead. 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 personal email handling 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 personal email handling 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

The pipeline treated every email domain as a company domain, so a personal address produced a nonsense company match.

Variant phrasings

lead enrichment error personal email enriched as work email 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 personal email handling 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 personal email handling 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: personal email handling 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/psthyjOORQ78Z3X4j99_sg

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

Thread query: lead enrichment error personal email enriched as work email failure

TL;DR: Fix this in personal email handling in enrichment by acting on the exact message first: flag free and personal email domains with a maintained freemail list, keep those leads out of company enrichment, and match them to a company only from an explicit company field on the lead. 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 the workspace enrichment setting by acting on the exact message first: check in the provider workspace settings that enrichment is enabled for the workspace the leads sit in, switch the job to that enabled workspace or have an admin enable it, and rerun one lead to confirm. 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.

lead enrichment failed error "enrichment disabled for this workspace" failure

Use this when

• The operation in the workspace enrichment setting fails with this exact message: lead enrichment failed error "enrichment disabled for this workspace" 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 the workspace enrichment setting, 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: check in the provider workspace settings that enrichment is enabled for the workspace the leads sit in, switch the job to that enabled workspace or have an admin enable it, and rerun one lead to confirm. 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 the workspace enrichment setting 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 the workspace enrichment setting 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

Enrichment was enabled on one workspace while the leads and the job lived in another where it was switched off.

Variant phrasings

lead enrichment failed error "enrichment disabled for this workspace" 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 the workspace enrichment setting

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 the workspace enrichment setting

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: the workspace enrichment setting 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_KsCTMxUAKf1EbVTR28cpjg

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

Thread query: lead enrichment failed error "enrichment disabled for this workspace" failure

TL;DR: Fix this in the workspace enrichment setting by acting on the exact message first: check in the provider workspace settings that enrichment is enabled for the workspace the leads sit in, switch the job to that enabled workspace or have an admin enable it, and rerun one lead to confirm. 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 RocketReach by acting on the exact message first: require the employer, location and work history to agree before accepting a profile match, reject matches whose current employer differs from the target company, and rematch using the company domain as a filter. 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.

RocketReach lookup matched a profile to a namesake at a different company, title wrong

Use this when

• The operation in RocketReach fails with this exact message: RocketReach lookup matched a profile to a namesake at a different company, title wrong.
• 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 RocketReach, 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: require the employer, location and work history to agree before accepting a profile match, reject matches whose current employer differs from the target company, and rematch using the company domain as a filter. 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 RocketReach 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 RocketReach 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 cannot separate two people with the same name, so the first profile returned won the match even though its employer was a different firm.

Variant phrasings

RocketReach lookup matched a profile to a namesake at a different company, title wrong

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 RocketReach

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 RocketReach

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: RocketReach 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/pst0VD3aCoF_BuDAOLiDxo-w

Resolved from the public thread: https://vectle.com/posts/pst0VD3aCoF_BuDAOLiDxo-w

Thread query: RocketReach lookup error profile matched to namesake at different company title wrong

TL;DR: Fix this in RocketReach by acting on the exact message first: require the employer, location and work history to agree before accepting a profile match, reject matches whose current employer differs from the target company, and rematch using the company domain as a filter. 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.