agent csv import mapped columns wrong: emails landed in name field

Not specified by the original author.

TL;DR

The import ran but the email column never mapped to the email property, usually because the header name did not match (E-mail vs Email vs email_address). Check the import's column mapping, fix the header, and re-import just the affected rows with the contact id as the key.

Error

(No error; the symptom is contacts with blank email after a successful import.)

Steps

1. Open the import record and review its column mapping. Expected: you see which CSV header mapped to the email property, or that none did.
2. Rename the CSV header to match exactly, or set the mapping manually in the import UI. Expected: email maps to the email property.
3. Export the affected contacts with their record ids. Expected: a file keyed by id for the fix-up import.
4. Re-import with the id as the dedupe key and the corrected email column. Expected: emails fill in on the existing contacts, no new duplicates.
5. Save the mapping as a template for future imports. Expected: the next import maps correctly on its own.

When to use

• Contacts lack emails after a CSV import.
• An agent-generated CSV imports with blank fields.
• Re-imports to fix the gap.

When not to use

• "invalid email address format" (bad values, not missing mapping).
• CONTACTALREADYEXISTS (dedupe, not mapping).

Tool compatibility

• HubSpot and Salesforce import UIs and APIs.
• CSV pipelines feeding either CRM.

Variant phrasings

import skipped the email column

The header did not match; map it manually.

blank fields after import

General mapping problem; check every column, not just email.

Why it happens

Import mappers guess from header names. Non-standard headers (E-mail Address, ContactEmail, e_mail) defeat the guesser silently, and the import "succeeds" with blanks.

Edge cases

• Re-importing without the record id as key creates duplicates; always include the id.
• Some imports trim headers; a header with a trailing space maps to nothing.
• Encoded CSVs (BOM, semicolons) can shift columns; validate the parse before mapping.

Provenance

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

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

Thread query: crm contacts missing email after csv import error

TL;DR: The import ran but the email column never mapped to the email property, usually because the header name did not match (E-mail vs Email vs email_address). Check the import's column mapping, fix the header, and re-import just the affected rows with the contact id as the key.

Not specified by the original author.

TL;DR

Fix this in the enrichment CSV import by acting on the exact message first: re-map the import columns explicitly so the email column points at the email field, check the header row for renamed or duplicated headers, and import ten rows as a test before the full file. 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 job failed error CSV column mapping wrong email field missing failure

Use this when

• The operation in the enrichment CSV import fails with this exact message: enrichment job failed error CSV column mapping wrong email field missing 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 enrichment CSV import, 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: re-map the import columns explicitly so the email column points at the email field, check the header row for renamed or duplicated headers, and import ten rows as a test before the full file. 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 enrichment CSV import 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 enrichment CSV import 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 importer mapped columns by position or by a guessed header, so the email values landed in another field and the email field arrived empty.

Variant phrasings

enrichment job failed error CSV column mapping wrong email field missing 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 enrichment CSV import

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 enrichment CSV import

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 enrichment CSV import 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/pstBKDAHdekXSc41zzusUszA

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

Thread query: enrichment job failed error CSV column mapping wrong email field missing failure

TL;DR: Fix this in the enrichment CSV import by acting on the exact message first: re-map the import columns explicitly so the email column points at the email field, check the header row for renamed or duplicated headers, and import ten rows as a test before the full file. 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 Broken redirect crawl agent by acting on the exact symptom first: detect the CSV delimiter and quoting from the header row, validate that every row has a source and a target address, reject malformed rows into a small error list, and parse the clean rows again. Do not repeat the same edit, search or run unchanged, because the same inputs produce the same failure. Prove the fix on one article, collection or query first, then apply it across the affected scope and confirm as a reader.

Parser failed on the redirect map CSV for crawling the help center for broken redirects

Use this when

• Work in Broken redirect crawl agent shows this exact symptom: Parser failed on the redirect map CSV for crawling the help center for broken redirects.
• The same symptom repeats after a retry with unchanged inputs.
• Readers or support agents are blocked until this item is corrected.

Not for this skill when

• The help center platform itself is down or returning outage notices. Resolve that first, then return here if this symptom remains.
• The content is correct and you only want a style or tone rewrite. That is an editorial pass, not this fix.

Steps

1. Reproduce the symptom with the smallest scope that still shows it in Broken redirect crawl agent, and record the article, collection or query involved plus the exact wording from the code block above. Verify: the symptom is reproduced on demand with a named scope, not only reported second hand.
2. Apply the specific fix for this symptom: detect the CSV delimiter and quoting from the header row, validate that every row has a source and a target address, reject malformed rows into a small error list, and parse the clean rows again. Verify: the smallest failing scope now behaves as the fix predicts, checked in the published view rather than only in the editor.
3. Check neighbouring articles, collections or locales that share the same template, category or workflow, because this class of problem rarely affects only one item. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Repeat the original reader or agent action in Broken redirect crawl agent that exposed the symptom, using the same query, link or workflow as the first attempt. Verify: the action completes and the original symptom does not appear.
5. Compare the result against the source of truth for this item, the current product behaviour, price list, release notes or ticket evidence named in the fix. Verify: the published result matches the source or every difference is named and explained.
6. Record the fix, the scope it covered and the verification result where the content team works, so the next occurrence is recognised immediately. Verify: the record names the symptom, the fix applied and the evidence of success.

Variant phrasings

Parser failed on the redirect map CSV for crawling the help center for broken redirects

The verbatim form readers and agents paste from the help center or console. Treat it identically: same fix, same single scope proof, then the wider rollout.

How to fix - parser failed on redirect map CSV for crawling the help center for broken redirects error parsing failure

The how to phrasing for the same problem in Broken redirect crawl agent. The steps above apply unchanged; start at the reproduction step rather than skipping to the final check.

Broken redirect crawl agent troubleshooting for this symptom

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

Why it happens

Redirect maps exported from a spreadsheet often carry quoted addresses containing commas, and a naive split on commas broke rows into the wrong fields.

Edge cases

• The symptom appears in one locale, collection or audience view only. Fix that scope, then check the same item in the other views before closing.
• A cached or indexed copy keeps showing the old state after the fix. Allow for the platform reindex or cache window, recheck in a fresh reader session, and only then escalate.
• Two items have near identical titles. Confirm the identifier of the item you edited, not just its title, before declaring the fix verified.

Compatibility: Broken redirect crawl agent at current versions, plus the help center admin, search or API surface the query names; no extra tooling beyond reader level access to verify the published result.

Provenance

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

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

Thread query: parser failed on redirect map CSV for crawling the help center for broken redirects error parsing failure

TL;DR: Fix this in Broken redirect crawl agent by acting on the exact symptom first: detect the CSV delimiter and quoting from the header row, validate that every row has a source and a target address, reject malformed rows into a small error list, and parse the clean rows again. Do not repeat the same edit, search or run unchanged, because the same inputs produce the same failure. Prove the fix on one article, collection or query first, then apply it across the affected scope and confirm as a reader.