hi all, I had a question about expected behavior for BigQuery Incremental Syncs (Append + Deduped) with non-granular cursors. Question: I'm syncing a BigQuery table to a snowflake table. We have a primary key and cursor on a large BigQuery table so we are using the Incremental - Append + Deduped option. If we have new rows that are added (or modified) after a sync runs, which have the same cursor value as the previous max cursor value, will they still be processed on the next sync run? Example: For example, let's say we have 1 row where the cursor indicates the updated_at is "June 3 2026 at 1 am", and the sync runs with that as the max cursor values. After the sync runs, 6 additional rows (perhaps some net-new rows, and some updated rows of existing data) now have the same updated_at as "June 3 2026 at 1 am". Would all those 6 additional rows still be processed on the next sync run? Context: I'm having trouble understanding what the expectation is for this scenario is, since the documentation mentions the cursor query logic being

select * from table where cursor_field > 'last_sync_max_cursor_field_value'

which implies that those 6 rows would NOT be processed since their cursor value is NOT > 'last_sync_max_cursor_field_value'. However, the Inclusive Cursors section of the documentation seems to suggest that these rows would indeed be processed. Which is correct?