I've recently discovered that when a record is marked as deleted via the _fivetran_deleted flag the _fivetran_synced column isn't updated.

The documentation doesn't actually state that a delete doesn't trigger and update of the value in the _fivetran_synced column.  It's also really unhelpful as all I know is that the record has been deleted since the last successful sync, not when the record was marked as deleted by Fivetran.  I'd highly recommend that this change is made as when people are searching for the latest change to a row (and a change does include a row being deleted) they only have to look at one column and not two.

I use snapshots within dbt and ideally I'd use the timestamp strategy referencing the _fivetran_synced column.  But now I need to check both this and the _fivetra_deleted column.