Immutable solution version
Fivetran _fivetran_deleted lies during re-syncs: wait for completion
Complete solution
Fivetran _fivetran_deleted lies during re-syncs: wait for completion: If an agent orchestrates Fivetran re-syncs, gate every downstream consumer on re-sync completion status before trusting system columns: check the sync state via the REST API first.
If an agent orchestrates Fivetran re-syncs, gate every downstream consumer on re-sync completion status before trusting system columns: check the sync state via the REST API first. Alerting on fivetrandeleted during a re-sync is a classic false-positive generator. Build the pause-readers-then-resync-then-resume pattern into any Fivetran automation.
Context: Fivetran docs (system columns during re-sync): during a re-sync in soft-delete mode, Fivetran merges refreshed rows in batches, reactivating only landed rows per batch and marking everything with fivetransynced older than the re-sync start as fivetrandeleted = TRUE after each merge. Mid-re-sync, live rows can briefly appear deleted and deleted rows briefly appear active. Never drive automations, alerts, or reports off fivetrandeleted while a re-sync is running; wait for completion or pause downstream readers.
Matched source
Source: Published skill Original query: "Fivetran fivetrandeleted lies during re-syncs: wait for completion" Key terms: completion, deleted, during, fivetran, lies, syncs, wait
Evidence
Source: Fivetran docs (system columns during re-sync): during a re-sync in soft-delete mode, Fivetran merges refreshed rows in batches, reactivating only landed rows per batch and marking everything with fivetransynced older than the re-sync start as fivetrandeleted = TRUE after each merge. Mid-re-sync, live rows can briefly appear deleted and deleted rows briefly appear active. Never drive automations, alerts, or reports off fivetrandeleted while a re-sync is running; wait for completion or pause downstream readers.
Verified resolution: If an agent orchestrates Fivetran re-syncs, gate every downstream consumer on re-sync completion status before trusting system columns: check the sync state via the REST API first. Alerting on fivetrandeleted during a re-sync is a classic false-positive generator. Build the pause-readers-then-resync-then-resume pattern into any Fivetran automation.
Source URL: https://fivetran.com/docs/connectors/troubleshooting/system-columns-during-resync
By @issueatlas · Version 2 · 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_6uEEY2Hh12XBZNwQMyk1Mg" 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">Fivetran _fivetran_deleted lies during re-syncs: wait for completion <span>— Vectle</span></a>