fix(docs): remove inaccurate statements

camunda · Nov 21, 2024 · 665c363 · 665c363
1 parent cde911d
commit 665c363
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 3 deletions.
diff --git a/versioned_docs/version-8.2/components/concepts/clusters.md b/versioned_docs/version-8.2/components/concepts/clusters.md
@@ -37,8 +37,10 @@ You can resume a paused cluster at any time, which typically takes five to ten m
 
 - Clusters tagged as `dev` (or untagged) auto-pause eight hours after the cluster is created or resumed from a paused state.
 - Clusters tagged as `test`, `stage`, or `prod` auto-pause if there is no cluster activity for 48 hours.
-- Paused `dev` (or untagged) clusters are automatically deleted after 30 consecutive paused days. You can change the tag to avoid cluster deletion.
-- No data is lost while a cluster is paused. All execution and configuration is saved, but cluster components such as Zeebe and Operate are temporarily disabled until you resume the cluster.
+- Cluster disk space is cleared when a trial cluster is paused.
+    - You will need to redeploy processes to the cluster once it is resumed from a paused state.
+    - Cluster configuration settings (for example, API Clients, Connector secrets, and IP allowlists) are saved so you can easily resume a cluster.
+
 
 :::tip
 To prevent auto-pause, [Upgrade your Free Trial plan](https://camunda.com/pricing/) to a Starter or Enterprise plan.

diff --git a/versioned_docs/version-8.6/components/concepts/clusters.md b/versioned_docs/version-8.6/components/concepts/clusters.md
@@ -76,7 +76,6 @@ You can resume a paused cluster at any time, which typically takes five to ten m
 
 - Clusters tagged as `dev` (or untagged) auto-pause eight hours after the cluster is created or resumed from a paused state.
 - Clusters tagged as `test`, `stage`, or `prod` auto-pause if there is no cluster activity for 48 hours.
-- Paused `dev` (or untagged) clusters are automatically deleted after 30 consecutive paused days. You can change the tag to avoid cluster deletion.
 - Cluster disk space is cleared when a trial cluster is paused.
   - You will need to redeploy processes to the cluster once it is resumed from a paused state.
   - Cluster configuration settings (for example, API Clients, Connector secrets, and IP allowlists) are saved so you can easily resume a cluster.