Why Are Some Deleted Records Not Reflected as Deleted in My Destination?

Question

Why are some deleted records not reflected as deleted in my destination?

Environment

Connector: GitHub

Answer

Due to GitHub API limitations, we only support capturing deletes for the MILESTONE, PROJECT, COLUMN, and CARD tables. For more information, see our GitHub connector features documentation.

To capture deletes for other tables, you must trigger a historical re-sync for your connection. For instructions on triggering historical re-syncs and the impact on your monthly active rows (MAR), see How to Trigger Historical Re-Syncs.

After the re-sync, your destination will contain both active and deleted records. To report only on non-deleted records, filter your queries to include rows synced during or after the re-sync. For example:

SELECT * FROM <destination_db>.<destination_schema>.REPOSITORY
WHERE _fivetran_synced >= time_of_re-sync