You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/connections/reverse-etl/index.md
+5Lines changed: 5 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -298,3 +298,8 @@ Column count | The maximum number of columns a single sync will process. | 512 c
298
298
Column name length | The maximum length of a record column. | 128 characters
299
299
Record JSON size | The maximum size for a record when converted to JSON (some of this limit is used by Segment). | 512 KiB
300
300
Column JSON size | The maximum size of any single column value. | 128 KiB
301
+
302
+
## FAQs
303
+
304
+
#### Why do my sync results show *No records extracted* when I select *Updated records* after I enable the mapping?
305
+
It's expected that when you select **Updated records** the records do not change after the first sync. During the first sync, the reverse ETL system calculates a snapshot of all the results and creates records in the `_segment_reverse_etl` schema. All the records are considered as *Added records* instead of *Updated records* at this time. The records can only meet the *Updated records* condition when the underlying values change after the first sync completes.
0 commit comments