Which connector?:

Hibob Connector, EMPLOYEE table

Additional details:

In the HiBob connector, when an employee is deleted at the source, Fivetran marks the destination row with _fivetran_deleted = true but does not update _fivetran_synced to the time of the sync that detected the deletion. The column keeps its old value from before the deletion.

Fivetran Support confirmed this is expected for bulk soft-deletes, which is how the EMPLOYEE table is handled.

Impact

We use _fivetran_synced as the watermark for our incremental models. Because a deletion doesn’t advance it, the models never pick up the change. Deleted employees stay active in our downstream tables, which leads to wrong headcount and reporting. _fivetran_synced can no longer be trusted to detect every change.

Request

When a row is marked _fivetran_deleted = true, whether individually or in bulk, _fivetran_synced should be set to the timestamp of the sync that detected the deletion.