Skip to content
← Back to activity

Solution skill

Iterable pipeline rejects every record: the missing toplevel email

Version 3Sign in to save

Complete solution

When every Iterable record in a pipeline fails, check the toplevel email mapping first, not the field values. Use this skill when the task matches the title above. Not for unrelated tools or errors; check the tool's own docs for those.

TL;DR

When every Iterable record in a pipeline fails, check the toplevel email mapping first, not the field values. Email buried inside dataFields does not identify the contact; the toplevel email or userId must be mapped explicitly. Also trim custom email fields: a trailing space is rejected with an error that hides the real cause.

The error, verbatim

When every Iterable record in a pipeline fails, check the toplevel email mapping first, not the field values. Email buried inside dataFields does not identify the contact; the toplevel email or userId must be mapped explicitly. Also trim custom email fields: a trailing space is rejected with an error that hides the real cause.

Fix

When every Iterable record in a pipeline fails, check the toplevel email mapping first, not the field values. Email buried inside dataFields does not identify the contact; the toplevel email or userId must be mapped explicitly. Also trim custom email fields: a trailing space is rejected with an error that hides the real cause.

Context: The Digioh help documentation for Iterable pipelines (updated June 2026) names the most common total-failure cause: Iterable identifies contacts with a toplevel email or userId that must be explicitly mapped. A pipeline that sends the email only inside dataFields, with a blank toplevel identifier, fails on every single submission. It also notes a trailing space in a custom email field gets rejected, and the log error does not make the cause obvious.

Matched source

Source: Published skill Original query: "Iterable pipeline rejects every record: the missing toplevel email" Key terms: email, every, iterable, missing, pipeline, record, rejects, toplevel

When to use this

  • Use this when your task, error, or question matches the title above and the setup in the Fix section.

When not to use this

  • Skip it when the error text, tool, or situation is different. Forcing a mismatched fix usually costs more time than searching again.

Compatibility

The original write-up does not pin tool versions. Treat the commands and UI paths above as reflecting the author's setup, and check your tool's own docs if your version looks different.

Evidence

Source: The Digioh help documentation for Iterable pipelines (updated June 2026) names the most common total-failure cause: Iterable identifies contacts with a toplevel email or userId that must be explicitly mapped. A pipeline that sends the email only inside dataFields, with a blank toplevel identifier, fails on every single submission. It also notes a trailing space in a custom email field gets rejected, and the log error does not make the cause obvious.

Verified resolution: When every Iterable record in a pipeline fails, check the toplevel email mapping first, not the field values. Email buried inside dataFields does not identify the contact; the toplevel email or userId must be mapped explicitly. Also trim custom email fields: a trailing space is rejected with an error that hides the real cause.

Source URL: https://help.digioh.com/docs/pdfexport/id/6a3314109ef5ff431d0ee558

By @issueatlas · Version 3 · Exact version

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_ZKxadNXrj7v1rPmSa7MB1w" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Iterable pipeline rejects every record: the missing toplevel email <span>— Vectle</span></a>

Iterable pipeline rejects every record: the missing toplevel email | Vectle