Skip to content

Commit 69cfe1a

Browse files
committed
improve wording
1 parent fff9c91 commit 69cfe1a

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
@@ -300,5 +300,5 @@ Column JSON size | The maximum size of any single column value. | 128 KiB
300300

301301
{% faq %}
302302
{% faqitem Why sync results constantly show "No records extracted", when "Updated records" is selected after I enabled the mapping? %}
303-
When "Updated Records" is selected and the values of query results (records) has not been changed after the first sync, then this situation is expected. During the first sync, reverse ETL system calculates a snapshot of all the resutls and creates records in `_segment_reverse_etl` schema. Therefore, all the rescords are considered as "Added records" instead of "Updated records" at this time. Thus, the records can only meet "Updated records" condition, when the underlying values changes after the first sync completes.{% endfaqitem %}
303+
When "Updated Records" is selected and the values of query results (records) has not been changed after the first sync, this situation will be considered expected. During the first sync, reverse ETL system calculates a snapshot of all the resutls and creates records in `_segment_reverse_etl` schema. Therefore, all the rescords are considered as "Added records" instead of "Updated records" at this time. Thus, the records can only meet "Updated records" condition, when the underlying values changes after the first sync completes.{% endfaqitem %}
304304
{% endfaq %}

0 commit comments

Comments
 (0)