From dc0c8fc611eb6d79fa76241bd79d250a91bd03f8 Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Thu, 29 Aug 2024 13:45:27 -0400 Subject: [PATCH 1/3] hide advance retries note --- src/connections/reverse-etl/manage-retl.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/connections/reverse-etl/manage-retl.md b/src/connections/reverse-etl/manage-retl.md index c449ac0c4d..45b3c888c5 100644 --- a/src/connections/reverse-etl/manage-retl.md +++ b/src/connections/reverse-etl/manage-retl.md @@ -40,8 +40,8 @@ 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. -> info "Segment automatically retries events that were extracted but failed to load" -> 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. +> info "Segment automatically retries events that were extracted but failed to load" +> 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. ---> ## Reset syncs You can reset your syncs so that your data is synced from the beginning. This means that Segment resyncs your entire dataset for the model. During the next sync, all records extracted by the model are sent to your destination, not just the records that changed since the last sync. From 65261d6dab8a0adba22b3ca9ea5389499f003015 Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Thu, 29 Aug 2024 13:55:48 -0400 Subject: [PATCH 2/3] [netlify-build] --- 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 45b3c888c5..dec1ea0048 100644 --- a/src/connections/reverse-etl/manage-retl.md +++ b/src/connections/reverse-etl/manage-retl.md @@ -138,4 +138,4 @@ Select array | This enables you to send all nested properties within the array. > success "" > Certain array mapping fields have a fixed list of properties they can accept. If the names of the nested properties in your array don't match the destination properties, the data won't send. Segment recommends you to use the **Customize array** option to ensure your mapping is successful. -Objects in an array don't need to have the same properties. If a user selects a missing property in the input object for a mapping field, the output object will miss the property. \ No newline at end of file +Objects in an array don't need to have the same properties. If a user selects a missing property in the input object for a mapping field, the output object will miss the property. From 4258ad8b8ffe4b0647e03d8f3a7a6f67b2fe8cf2 Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Thu, 29 Aug 2024 14:09:17 -0400 Subject: [PATCH 3/3] [netlify-build] --- 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 dec1ea0048..63f68cd90b 100644 --- a/src/connections/reverse-etl/manage-retl.md +++ b/src/connections/reverse-etl/manage-retl.md @@ -40,7 +40,7 @@ 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. -> info "Segment automatically retries events that were extracted but failed to load" + ## Reset syncs