diff --git a/.generated-info b/.generated-info
index 8a6747241a39..1a9005895097 100644
--- a/.generated-info
+++ b/.generated-info
@@ -1,4 +1,4 @@
 {
-  "spec_repo_commit": "c09ac23",
-  "generated": "2025-07-24 19:57:54.130"
+  "spec_repo_commit": "d51e9a8",
+  "generated": "2025-07-25 13:23:07.308"
 }
diff --git a/features/v2/data_deletion.feature b/features/v2/data_deletion.feature
index 4085e586ba13..6bfc942e2a72 100644
--- a/features/v2/data_deletion.feature
+++ b/features/v2/data_deletion.feature
@@ -17,7 +17,7 @@ Feature: Data Deletion
     When the request is sent
     Then the response status is 400 Bad Request
 
-  @team:DataDog/supportability-engineering
+  @replay-only @team:DataDog/supportability-engineering
   Scenario: Cancels a data deletion request returns "OK" response
     Given operation "CancelDataDeletionRequest" enabled
     And there is a valid "deletion_request" in the system
@@ -47,7 +47,7 @@ Feature: Data Deletion
     When the request is sent
     Then the response status is 400 Bad Request
 
-  @team:DataDog/supportability-engineering
+  @replay-only @team:DataDog/supportability-engineering
   Scenario: Creates a data deletion request returns "OK" response
     Given operation "CreateDataDeletionRequest" enabled
     And new "CreateDataDeletionRequest" request
@@ -75,7 +75,7 @@ Feature: Data Deletion
     When the request is sent
     Then the response status is 400 Bad Request
 
-  @team:DataDog/supportability-engineering
+  @replay-only @team:DataDog/supportability-engineering
   Scenario: Gets a list of data deletion requests returns "OK" response
     Given operation "GetDataDeletionRequests" enabled
     And there is a valid "deletion_request" in the system