diff --git a/_data/nav.yml b/_data/nav.yml
index 36a8ecaba..d8a32fb83 100644
--- a/_data/nav.yml
+++ b/_data/nav.yml
@@ -380,9 +380,7 @@
         - title: Secrets for pipelines
           url: "/secrets-store"  
         - title: Public logs and status badges
-          url: "/build-status"
-        - title: Build retention policy
-          url: "/build-retention-policy"   
+          url: "/build-status"  
     - title: Steps in pipelines
       url: "/steps"
       sub-pages:
diff --git a/_docs/pipelines/configuration/build-retention-policy.md b/_docs/pipelines/configuration/build-retention-policy.md
deleted file mode 100644
index 6b469d012..000000000
--- a/_docs/pipelines/configuration/build-retention-policy.md
+++ /dev/null
@@ -1,52 +0,0 @@
----
-title: "Configure build retention policy for pipelines"
-description: "Define workflow retention"
-group: pipelines
-sub_group: configuration
-toc: true
----
-
-Define the retention policy for pipeline builds in your environments. 
-
-For existing environments, save storage space by deleting older builds. Fewer pipeline builds to manage, make it easy to navigate to and find relevant builds for monitoring and troubleshooting. 
-For new environments, defining a retention policy to better control build environments and optimize storage space. 
-
-Retention settings are controlled through environment variables in `cf-api`. By default, when enabled, Codefresh implements a Cron job that deletes removes data from the `workflowproccesses` collection. 
-
->**NOTE**:  
-  Build logs are _not_ deleted.
-
-
-
-## Pipeline build retention settings
-
-
-{: .table .table-bordered .table-hover}
-| Env Variable   | Description             | Default                |
-|---------------|--------------------------- |----------------------  |
-|`TTL_RETENTION_POLICY_IS_ENABLED` | Determines if automatic build deletion through the Cron job is enabled.         | `false`                 |
-|`TTL_RETENTION_POLICY_IN_DAYS`    | The number of days for which to retain builds, and can be between `30` (minimum) and `365` (maximum). Builds older than the defined retention period are deleted.  | `365`              |
-
-
-
-
-## (Optional) Drop MongoDB index for existing environments
-
-For existing environments, for the retention mechanism to work, you must first drop the existing index in MongoDB.  
-This action requires a maintenance window that depends on the number of workflows to delete, approximately three hours per MongoDB node. 
-
-1. In MongoDB, drop the index for `created` field in `workflowprocesses` collection.
-1. Continue with _Configure build retention policy_.
-
-## Configure build retention policy
-If you have more than one `cf-api`, you must configure _all_ of them.
-
-1. In `cf-api`, add `env.TTL_RETENTION_POLICY_IS_ENABLED`, and set it to `true`.
-1. Add `TTL_RETENTION_POLICY_IN_DAYS` and set to the required value. If not set, uses the default of `365` days.
-1. Verify that the `created` field in the `workflowprocesses` collection has a new index.   
-1. Restart `cf-api`.
-   
-## Related articles
-[Creating pipelines]({{site.baseurl}}/docs/pipelines/pipelines/)  
-[Monitoring pipelines]({{site.baseurl}}/docs/pipelines/monitoring-pipelines/)  
-[Pipeline integrations with Codefresh API]({{site.baseurl}}/docs/integrations/codefresh-api/)  
\ No newline at end of file
diff --git a/_posts/2023-05-29-may-release-notes.md b/_posts/2023-05-29-may-release-notes.md
index 8742b7a5f..ad4fecdcd 100644
--- a/_posts/2023-05-29-may-release-notes.md
+++ b/_posts/2023-05-29-may-release-notes.md
@@ -82,6 +82,7 @@ max-width="60%"
 ### Pipelines: New layout for Helm Boards
 Helm Boards now display information in a horizontal layout. The new layout prevents fields with long names from overlapping with each other.
 
+<!-- 
 ### Pipelines: Automated build deletion
 Set the desired time-to-live (TTL) for your builds to automatically remove older builds and free up valuable storage resources in your build environments. Fewer builds also make it easier to navigate to and find relevant builds for monitoring and troubleshooting.
 
@@ -89,6 +90,7 @@ Take advantage of the `TTL_RETENTION_POLICY_IS_ENABLED` and `TTL_RETENTION_POLIC
 
 For details, see [Configure build retention policy for pipelines]({{site.baseurl}}/docs/pipelines/configuration/build-retention-policy/).
 
+-->
 
 ### Preferred date and time format selection
 US and international users can select their preferred format for date and time in the Codefresh UI. With this latest enhancement, you can now choose between US and international date formats, as well as 24 or 12-hour time formats, to best suit your needs.