diff --git a/tests/ten/ten_cor_027/pysystest.xml b/tests/ten/ten_cor_027/pysystest.xml
index b27be8af..eb6a8d4d 100644
--- a/tests/ten/ten_cor_027/pysystest.xml
+++ b/tests/ten/ten_cor_027/pysystest.xml
@@ -13,7 +13,6 @@ as the account performing the transfer. Validates that the event is seen and wit
 
     <classification>
         <groups inherit="true">
-            <group>skip</group>
             <group>bridge</group>
         </groups>
         <modes inherit="true">
diff --git a/tests/ten/ten_cor_031/pysystest.xml b/tests/ten/ten_cor_031/pysystest.xml
index 8dcd2cb1..962675e3 100644
--- a/tests/ten/ten_cor_031/pysystest.xml
+++ b/tests/ten/ten_cor_031/pysystest.xml
@@ -8,15 +8,12 @@ In the test we have a user that deploys and transacts against the Storage contra
 it's own connection. Another connection is created with two registered users, and a single subscription is made to all
 event logs from the network. Since the Storage Store event is a lifecycle event, and we subscribe to all event logs from
 the network, we expect a single call back for our subscriber (de-duplication).
-
-Skipped due to https://github.com/ten-protocol/ten-internal/issues/4297
 ]]>
         </purpose>
     </description>
 
     <classification>
         <groups inherit="true">
-            <group>skip</group>
             <group>gateway</group>
         </groups>
         <modes inherit="true">