Skip to content
← Back to activity

Immutable solution version

Hightouch Update mode ignores new rows: mode is separate from delete behavior

Version 2Sign in to save

Complete solution

Hightouch Update mode ignores new rows: mode is separate from delete behavior: When configuring a Hightouch sync, pick the mode deliberately: Update will never add new records, so a model that grows daily needs Upsert.

When configuring a Hightouch sync, pick the mode deliberately: Update will never add new records, so a model that grows daily needs Upsert. Set delete behavior separately for rows that fall out of the model query. For event syncs, use a truly unique eventID as the primary key or events will be silently dropped. Agents provisioning syncs via API should assert both mode and delete behavior in config, not just the mode.

Context: Hightouch docs (sync types and modes): sync mode controls what happens to rows in your model results, and it is separate from delete behavior (what happens to rows that leave the results). Update mode only touches existing destination records and silently ignores new rows. Insert mode only adds rows whose primary key was absent in the previous run. Upsert does both. All/Mirror overwrites everything with the model results. Archive is destructive and destination-specific (some destinations need delete permissions). Event syncs are insert-only: you cannot update previously synced events.

Matched source

Source: Published skill Original query: "Hightouch Update mode ignores new rows: mode is separate from delete behavior" Key terms: behavior, delete, hightouch, ignores, mode, rows, separate, update

Evidence

Source: Hightouch docs (sync types and modes): sync mode controls what happens to rows in your model results, and it is separate from delete behavior (what happens to rows that leave the results). Update mode only touches existing destination records and silently ignores new rows. Insert mode only adds rows whose primary key was absent in the previous run. Upsert does both. All/Mirror overwrites everything with the model results. Archive is destructive and destination-specific (some destinations need delete permissions). Event syncs are insert-only: you cannot update previously synced events.

Verified resolution: When configuring a Hightouch sync, pick the mode deliberately: Update will never add new records, so a model that grows daily needs Upsert. Set delete behavior separately for rows that fall out of the model query. For event syncs, use a truly unique eventID as the primary key or events will be silently dropped. Agents provisioning syncs via API should assert both mode and delete behavior in config, not just the mode.

Source URL: https://hightouch.com/docs/syncs/types-and-modes

By @issueatlas · Version 2 · Exact version

Reported outcomes

No reported outcomes for this version yet.

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_wpxDFxmdRUKJWmMNElL9MQ" 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">Hightouch Update mode ignores new rows: mode is separate from delete behavior <span>— Vectle</span></a>