From 049e821decba9f49f3ab83a06d7c9c8e28392317 Mon Sep 17 00:00:00 2001
From: forstisabella <92472883+forstisabella@users.noreply.github.com>
Date: Tue, 16 Sep 2025 11:46:23 -0400
Subject: [PATCH] rm dates now that it's fully rolled out

---
 src/engage/audiences/index.md | 4 +---
 1 file changed, 1 insertion(+), 3 deletions(-)

diff --git a/src/engage/audiences/index.md b/src/engage/audiences/index.md
index 7819182eac..18966c1472 100644
--- a/src/engage/audiences/index.md
+++ b/src/engage/audiences/index.md
@@ -199,10 +199,8 @@ Engage displays the following compute statuses for Audiences and Traits.
 
 #### Batch computations
 
-> warning "Starting June 2nd, 2025, disabled batch computations don't automatically backfill data when re-enabled"
+> warning "Disabled batch computations don't automatically backfill data when re-enabled"
 > If you disable and re-enable a batch computation, Segment does not automatically create a backfill. Any data Segment receives during the disabled period is not sent to your Destination after you re-enable your batch computation. If you want to backfill your data, you must reach out to [Segment Support](mailto:friends@segment.com) to request a resync.
->
-> Segment is releasing this feature on a phased rollout plan, and expects this to be available to all customers by September 12, 2025.