diff --git a/docs/components/concepts/clusters.md b/docs/components/concepts/clusters.md index 59408dc166..16c7e6a77a 100644 --- a/docs/components/concepts/clusters.md +++ b/docs/components/concepts/clusters.md @@ -76,8 +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. -- 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. diff --git a/versioned_docs/version-8.2/components/concepts/clusters.md b/versioned_docs/version-8.2/components/concepts/clusters.md index 7d96ec32d5..c83b48d12a 100644 --- a/versioned_docs/version-8.2/components/concepts/clusters.md +++ b/versioned_docs/version-8.2/components/concepts/clusters.md @@ -37,8 +37,9 @@ 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.3/components/concepts/clusters.md b/versioned_docs/version-8.3/components/concepts/clusters.md index f0348b3082..7bd3ce5dee 100644 --- a/versioned_docs/version-8.3/components/concepts/clusters.md +++ b/versioned_docs/version-8.3/components/concepts/clusters.md @@ -38,8 +38,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. -- 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. diff --git a/versioned_docs/version-8.4/components/concepts/clusters.md b/versioned_docs/version-8.4/components/concepts/clusters.md index db4bad1a4a..94ba72f05f 100644 --- a/versioned_docs/version-8.4/components/concepts/clusters.md +++ b/versioned_docs/version-8.4/components/concepts/clusters.md @@ -38,8 +38,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. -- 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. diff --git a/versioned_docs/version-8.5/components/concepts/clusters.md b/versioned_docs/version-8.5/components/concepts/clusters.md index bef1699122..c1febb2311 100644 --- a/versioned_docs/version-8.5/components/concepts/clusters.md +++ b/versioned_docs/version-8.5/components/concepts/clusters.md @@ -38,8 +38,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. -- 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. diff --git a/versioned_docs/version-8.6/components/concepts/clusters.md b/versioned_docs/version-8.6/components/concepts/clusters.md index b54b14f348..2df77d7295 100644 --- a/versioned_docs/version-8.6/components/concepts/clusters.md +++ b/versioned_docs/version-8.6/components/concepts/clusters.md @@ -76,8 +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. -- 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.