As part of the Coupa, Navan,concur aconnectors, during Re-import or Full Load operations, we observed that the existing destination data is being cleaned up and reloaded. During this process, the _fivetran_synced timestamp is updated only for the records that are reloaded or changed, while historical records are retained through Fivetran's deleted-record handling mechanism. This behavior makes it difficult to identify actual source data changes versus records affected by the re-import/full load process. Requesting a review of the re-import/full load strategy to preserve historical auditability and avoid unnecessary updates to _fivetran_synced when no source data changes have occurred.