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
+10Lines changed: 10 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -303,3 +303,13 @@ Column JSON size | The maximum size of any single column value. | 128 KiB
303
303
304
304
#### Why do my sync results show *No records extracted* when I select *Updated records* after I enable the mapping?
305
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.
306
+
307
+
#### Can I be notified when Reverse ETL syncs fail?
308
+
Yes, you can sign up for Reverse ETL sync notifications.
309
+
310
+
To receive Reverse ETL sync notifications:
311
+
1. Navigate to **Settings > User Preferences**.
312
+
2. Select **Reverse ETL** In the **Activity Notifications** section.
313
+
3. Enable the toggle for **Reverse ETL Sync Failed**.
314
+
315
+
In case of consecutive failures, Segment sends notifications for every sync failure. Segment doesn't send notifications for partial failures.
0 commit comments