From 50f4aaae4ed178afae7358001f1db529525aed94 Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Tue, 10 Dec 2024 13:48:07 -0500 Subject: [PATCH 1/5] Update manage-retl.md --- src/connections/reverse-etl/manage-retl.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/src/connections/reverse-etl/manage-retl.md b/src/connections/reverse-etl/manage-retl.md index 8925479ffe..b2114ea739 100644 --- a/src/connections/reverse-etl/manage-retl.md +++ b/src/connections/reverse-etl/manage-retl.md @@ -31,9 +31,12 @@ To check the status of your extractions: * The load results - how many successful records were synced as well as how many records were updated, deleted, or are new. 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. - - ## Reset syncs Reverse ETL uses the Unique Identifier column to detect data changes, like new, updated, and deleted records. If you encounter an error, you can reset Segment’s tracking of this column and force Segment to manually add all records from your dataset. From b29b223e3e70f397b7844067e47c6c2a61e5dd07 Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Wed, 11 Dec 2024 12:36:27 -0500 Subject: [PATCH 2/5] fix language --- src/connections/reverse-etl/manage-retl.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/connections/reverse-etl/manage-retl.md b/src/connections/reverse-etl/manage-retl.md index b2114ea739..b97d6b5b68 100644 --- a/src/connections/reverse-etl/manage-retl.md +++ b/src/connections/reverse-etl/manage-retl.md @@ -35,7 +35,7 @@ To check the status of your extractions: ## Automatic retry handling > info "Automatic retry handling feature might not yet be available in your workspace" -> To ensure overall system stability and performance, Segment is releasing automatic retry handling to all workspaces in a phased rollout program. Segment expects this feature to be available customers by January 31, 2025. +> To ensure overall system stability and performance, Segment is releasing automatic retry handling to all workspaces in a phased rollout program. Segment expects this feature to be available to all customers by January 31, 2025. Segment automatically retries events that were extracted from your data warehouse but failed to load for up to 14 days or 5 syncs following a partially successful sync or a sync failure. From a3079ae8caeb4ab9321f3e2c7c96483363b300b0 Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Wed, 11 Dec 2024 13:03:21 -0500 Subject: [PATCH 3/5] Update src/connections/reverse-etl/manage-retl.md Co-authored-by: pwseg <86626706+pwseg@users.noreply.github.com> --- src/connections/reverse-etl/manage-retl.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/connections/reverse-etl/manage-retl.md b/src/connections/reverse-etl/manage-retl.md index b97d6b5b68..5bc3e81655 100644 --- a/src/connections/reverse-etl/manage-retl.md +++ b/src/connections/reverse-etl/manage-retl.md @@ -34,7 +34,7 @@ To check the status of your extractions: ## Automatic retry handling -> info "Automatic retry handling feature might not yet be available in your workspace" +> info "Automatic retry handling might not yet be available in your workspace" > To ensure overall system stability and performance, Segment is releasing automatic retry handling to all workspaces in a phased rollout program. Segment expects this feature to be available to all customers by January 31, 2025. Segment automatically retries events that were extracted from your data warehouse but failed to load for up to 14 days or 5 syncs following a partially successful sync or a sync failure. From 93ea417f00be4b79f962b36e02856daca3ea1fb2 Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Wed, 11 Dec 2024 18:38:40 -0500 Subject: [PATCH 4/5] Update src/connections/reverse-etl/manage-retl.md --- src/connections/reverse-etl/manage-retl.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/connections/reverse-etl/manage-retl.md b/src/connections/reverse-etl/manage-retl.md index 5bc3e81655..f6ce244f3a 100644 --- a/src/connections/reverse-etl/manage-retl.md +++ b/src/connections/reverse-etl/manage-retl.md @@ -41,7 +41,7 @@ Segment automatically retries events that were extracted from your data warehous Segment checks for the latest changes in your data before loading the failed records on a subsequent (automatically scheduled or manually triggered) sync to ensure the data loaded into Segment isn’t stale and only the latest version of the data is loaded to destination. If the error causing the load failure is coming from an upstream tool, you can fix the error in the upstream tool to resolve the load error on a subsequent sync. -> warning "Syncs with intervals less than one hour may not see failed events on the sync immediately following failed record" +> warning "Syncs with intervals less than or equal to two hours may not see failed events on the sync immediately following failed record" > Syncs with intervals less than or equal to one hour may not see failed events right away, as Segment's internal systems take up to one hour to retry events that initially failed. ## Reset syncs From 84a90b71d669efc7ab8da7c1afe243d70cd35b2b Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Wed, 11 Dec 2024 18:42:00 -0500 Subject: [PATCH 5/5] Update src/connections/reverse-etl/manage-retl.md --- src/connections/reverse-etl/manage-retl.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/connections/reverse-etl/manage-retl.md b/src/connections/reverse-etl/manage-retl.md index f6ce244f3a..938694852d 100644 --- a/src/connections/reverse-etl/manage-retl.md +++ b/src/connections/reverse-etl/manage-retl.md @@ -42,7 +42,7 @@ Segment automatically retries events that were extracted from your data warehous Segment checks for the latest changes in your data before loading the failed records on a subsequent (automatically scheduled or manually triggered) sync to ensure the data loaded into Segment isn’t stale and only the latest version of the data is loaded to destination. If the error causing the load failure is coming from an upstream tool, you can fix the error in the upstream tool to resolve the load error on a subsequent sync. > warning "Syncs with intervals less than or equal to two hours may not see failed events on the sync immediately following failed record" -> Syncs with intervals less than or equal to one hour may not see failed events right away, as Segment's internal systems take up to one hour to retry events that initially failed. +> Syncs with intervals less than or equal to two hours may not see failed events right away, as Segment's internal systems take up to two hours to retry events that initially failed. ## Reset syncs Reverse ETL uses the Unique Identifier column to detect data changes, like new, updated, and deleted records. If you encounter an error, you can reset Segment’s tracking of this column and force Segment to manually add all records from your dataset.