Skip to content

Commit e3b1fb1

Browse files
committed
fix style
1 parent 62fbb58 commit e3b1fb1

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

src/connections/reverse-etl/index.md

Lines changed: 3 additions & 3 deletions
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

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** and 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.
304+
#### Why do my sync results show "**No records extracted**" when I select "**Updated records**" after I enable the mapping?
305+
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)