diff --git a/src/connections/reverse-etl/manage-retl.md b/src/connections/reverse-etl/manage-retl.md
index b03b681ad5..4bc6e04093 100644
--- a/src/connections/reverse-etl/manage-retl.md
+++ b/src/connections/reverse-etl/manage-retl.md
@@ -31,6 +31,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.
 
+<!--- IG 9/2024 - EM for RETL asked me to roll back the docs for this feature on 9/25/24!
 ## Automatic retry handling
 
 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. 
@@ -40,6 +41,8 @@ Segment checks for the latest changes in your data before loading the failed rec
 > warning "Syncs with intervals less than one hour 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
 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.