Why Does Sync History Show Extracted Rows but No Loaded Rows?

Question

Why does Fivetran show extracted rows but no loaded rows for a table in my connection's Sync History chart?

Environment

All API connectors

Answer

A table may show extracted rows but no loaded rows when Fivetran processes parent records from an API response, but the nested data used to populate the table is empty or null.

The extracted row count represents records processed before we flatten, filter, and transform nested data. The loaded row count represents rows synced to the destination after this processing. Therefore, we may count the parent records as extracted without syncing rows to the corresponding child table.

This is expected behavior, and no action is required.

Slack example

Let's say a Slack connection's PROFILE_FIELD_POSSIBLE_VALUE table shows 28 extracted rows but 0 loaded rows. This means Slack returned 28 profile_field records, but each record contained an empty possible_values list. We counted the parent records as extracted, but there were no child values to sync to the destination.