A data source reset fixed it. Not sure if that will a permanent solution going forward though.

Hey Jonas, incremental syncs operate with an at least once guarantee, meaning records may be duplicated (it heavily depends on the specific source connector's implementation) but records should never be missed

Thanks @George Claireaux (Airbyte)! Am a bit new to this field. What's the common way to deal with this, is it the hash ID one uses to dedeplicate?

DISTINCT _airbyte_field_name_hashid

Many connectors support Deduped History mode which should do what you're looking for 🙂 That docs page also walks through the logic for obtaining the deduped records

👍. Gotcha! many thanks