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/manage-retl.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -40,7 +40,7 @@ To check the status of your extractions:
40
40
* The load results - how many successful records were synced as well as how many records were updated, deleted, or are new.
41
41
5. If your sync failed, click the failed reason to get more details on the error and view sample payloads to help troubleshoot the issue.
42
42
43
-
<!--->> info "Segment automatically retries events that were extracted but failed to load"
43
+
<!--- info "Segment automatically retries events that were extracted but failed to load"
44
44
> Segment retries events for 14 days following a total or partial sync failure. Before loading the failed records on a subsequent sync, Segment checks for the latest changes in your data to ensure the data loaded into your warehouse isn't stale. If the error causing the load failure is coming from an upstream tool, you can fix the error in the upstream tool to ensure the record loads on the next sync. --->
0 commit comments