Manage and Troubleshoot Data Warehouse Syncs

​

Connection States

​

Open a Connection

• Sync shows the next scheduled sync, the duration of the last completed sync, the number of records synced, the tables updated, and a sync history table with one row per run: timestamp, target table, rows inserted or updated, and error count. Filter the history by date range or to hide empty syncs.
• Connection Details shows the credentials and database details. Secrets are stored securely and never displayed. For Snowflake connections this tab also holds the Storage Setup SQL and, for exports, the Table Creation SQL.

​

Pause and Resume

• A source agreement was broken. On an import connection that reads a table as it is, a mapped column was renamed or dropped, or the ID or modified date stopped meeting its rule. The error names the column. Fix the source, or update the mapping, then resume.
• Credentials expired or were rotated. Update them under Connection Details, then resume.
• Repeated sync failures. Check the sync history for the error, then resume once the cause is fixed.

​

Change Credentials and Settings

1. Open the connection and click Connection Details.
2. Click Edit Details. The sync pauses while you edit.
3. Update the fields and save. For an import connection you can re-enter secrets without redoing setup, then test the connection again.

​

Change the Sync Schedule

​

Delete a Connection

​

Remove an Object from a Connection

1. Open the connection and go to Set up your data.
2. Select the object in the left rail.
3. Click Remove from connection, then click Remove to confirm.

​

Change Your Source Tables Safely

• Adding columns is safe. New columns appear as unmapped sources in Unified Mapping and change nothing until you map them.
• Renaming or dropping a mapped column pauses the sync. The error names the column. Before you rename or remove a column that Inflection reads, remove its mapping in Unified Mapping first, or coordinate with your Inflection team.
• Sequence larger changes. If you are adding new columns while retiring old ones, add the new columns first, confirm they sync, and drop the old ones as a separate later step.
• A full resync follows a schema fix. Once the table is repaired, Inflection resyncs it in full. Timing depends on volume and is typically within a day. Avoid structural changes right before a time-sensitive send.

​

How Inflection Handles Duplicates and Deletes

​

Sync Timing

• A change in your warehouse shows in Inflection after the next scheduled sync, not instantly. Before assuming something is broken, compare when the last sync completed with when the source changed.
• Inflection syncs incrementally using the modified date or event timestamp you confirmed during setup. Rows whose timestamp falls outside the window since the last sync are not picked up. Add a column that records the real insert or update time, such as updated_at, so late-arriving rows are caught.
• Organizations and product users must land before their activity. If an activity event arrives before the matching user or organization exists, it has nothing to attach to and looks missing until the user record catches up. Keep the user, organization, and activity tables syncing on aligned intervals, and do not let user data lag behind activity.
• After activation, the schedule takes up to five minutes to register. During that window the page may show Next sync paused and a manual first sync may not start. Wait and try again.

​

Before a Large Backfill

​

Troubleshooting

-- Users referenced by activity that do not exist in the users table
SELECT COUNT(*)
FROM <schema>.product_activity a
LEFT JOIN <schema>.product_users u ON u.id = a.product_user_id
WHERE u.id IS NULL;

-- Membership rows whose user does not exist
SELECT COUNT(*)
FROM <schema>.product_user_organization m
LEFT JOIN <schema>.product_users u ON u.id = m.user_id
WHERE u.id IS NULL;