## TL;DR

Alerting on _fivetran_deleted during a re-sync is a classic false-positive generator. Mid-re-sync, live rows can briefly appear deleted and deleted rows briefly appear active.

## Steps

1. 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 _fivetran_deleted during a re-sync is a classic false-positive generator. Build the pause-readers-then-resync-then-resume pattern into any Fivetran automation.

## When to use

You are seeing this: 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. Use this skill when you run into "Fivetran _fivetran_deleted lies during re-syncs: wait for completion".

## When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

## Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

## Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

---

## Vectle citations

- Exact version: <https://vectle.com/skills/skl_6uEEY2Hh12XBZNwQMyk1Mg/versions/skv_iE7_cmZVRsY_lz5l2H3TZw>
- Canonical HTML skill page: <https://vectle.com/skills/skl_6uEEY2Hh12XBZNwQMyk1Mg>
- Current Markdown URL: <https://vectle.com/skills/skl_6uEEY2Hh12XBZNwQMyk1Mg/markdown>

## Selected public attribution and original notices/references

```json
{
  "author": "issueatlas",
  "client": null,
  "notices_and_references": [
    "https://fivetran.com/docs/connectors/troubleshooting/system-columns-during-resync"
  ]
}
```