Skip to content

Commit 0fe57f5

Browse files
committed
moving FAQs one level up as a section
1 parent e3b1fb1 commit 0fe57f5

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

src/connections/reverse-etl/index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -299,7 +299,7 @@ Column name length | The maximum length of a record column. | 128 characters
299299
Record JSON size | The maximum size for a record when converted to JSON (some of this limit is used by Segment). | 512 KiB
300300
Column JSON size | The maximum size of any single column value. | 128 KiB
301301

302-
### FAQs
302+
## FAQs
303303

304304
#### Why do my sync results show "**No records extracted**" when I select "**Updated records**" after I enable the mapping?
305305
It's expected when you select **Updated records** and the records did 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

Comments
 (0)