Remove auto-pause note (#4374)

* Remove auto-pause note * Backport to 8.5 * Backport to 8.4 * Backport to 8.3
camunda · Oct 1, 2024 · f63a224 · f63a224
1 parent d2bd977
commit f63a224
Show file tree

Hide file tree

Showing 8 changed files with 0 additions and 34 deletions.
diff --git a/docs/components/concepts/clusters.md b/docs/components/concepts/clusters.md
@@ -71,7 +71,3 @@ Additionally in the Starter Plan, the following applies to **development cluster
 
 - **Cluster is not highly available & includes less hardware**: Reduced hardware resources and availability compared to production cluster (for example, one Zeebe node only).
 - **Shorter history of processes and decisions**: Data retention in Operate, Optimize, and Tasklist is reduced to one day. For example, pending or historical process instances are deleted after one day as per the [fair usage limits of the Starter plan](https://camunda.com/legal/fair-usage-limits-for-starter-plan/).
-
-:::caution
-**Cluster auto-pause** is not yet available and only applies to non-Enterprise clusters. Development clusters will be paused if they go unused for two hours. When a cluster is paused, not all functionality is limited. For example, you may still execute BPMN timers and BPMN message catch events. To resume your cluster, review [how to resume a cluster](/components/console/manage-clusters/manage-cluster.md#resume-a-cluster).
-:::
diff --git a/docs/components/console/manage-clusters/create-cluster-include.md b/docs/components/console/manage-clusters/create-cluster-include.md
@@ -48,7 +48,3 @@ Users without **Admin** roles can deploy only on `dev`, `test`, or `stage` clust
 ![cluster-healthy](./img/cluster-overview-new-cluster-healthy.png)
 
 3. After the cluster is created, click on the cluster name to visit the cluster detail page.
-
-:::note
-**Cluster auto-pause** is not yet available and only applies to non-Enterprise clusters. Development clusters will be paused if they go unused for two hours. When a cluster is paused, not all functionality is limited. For example, you may still execute BPMN timers and BPMN message catch events. To resume your cluster, review [how to resume a cluster](/components/console/manage-clusters/manage-cluster.md#resume-a-cluster).
-:::
diff --git a/docs/components/console/manage-clusters/manage-cluster.md b/docs/components/console/manage-clusters/manage-cluster.md
@@ -18,10 +18,6 @@ A cluster can be renamed at any time. To rename your cluster, follow the steps b
 
 ## Resume a cluster
 
-:::note
-**Cluster auto-pause** is not yet available and only applies to non-Enterprise clusters. Development clusters will be paused if they go unused for two hours. When a cluster is paused, not all functionality is limited. For example, you may still execute BPMN timers and BPMN message catch events. To learn more about automatic cluster pausing on Free Trial plan clusters, see [auto-pause](/components/concepts/clusters.md#auto-pause).
-:::
-
 You can resume your paused cluster during deployment, or from the **Console** at any time.
 
 ### Resume during deployment

diff --git a/versioned_docs/version-8.3/components/concepts/clusters.md b/versioned_docs/version-8.3/components/concepts/clusters.md
@@ -61,9 +61,3 @@ Additionally, the following applies to **development clusters**:
 
 - **Cluster is not high-available & less hardware**: Reduced hardware resources and availability compared to production cluster (for example, one Zeebe node only).
 - **Shorter history of processes and decisions**: Data retention in Operate, Optimize, and Tasklist is reduced to one day. For example, pending or historical process instances are deleted after one day.
-
-:::caution
-
-**Cluster auto-pause** is not yet available. Development clusters will be paused if they go unused for two hours. When a cluster is paused, not all functionality will work, including BPMN timers and BPMN message catch events.
-
-:::
diff --git a/versioned_docs/version-8.4/components/concepts/clusters.md b/versioned_docs/version-8.4/components/concepts/clusters.md
@@ -71,7 +71,3 @@ Additionally in the Starter Plan, the following applies to **development cluster
 
 - **Cluster is not highly available & includes less hardware**: Reduced hardware resources and availability compared to production cluster (for example, one Zeebe node only).
 - **Shorter history of processes and decisions**: Data retention in Operate, Optimize, and Tasklist is reduced to one day. For example, pending or historical process instances are deleted after one day as per the [fair usage limits of the Starter plan](https://camunda.com/legal/fair-usage-limits-for-starter-plan/).
-
-:::caution
-**Cluster auto-pause** is not yet available and only applies to non-Enterprise clusters. Development clusters will be paused if they go unused for two hours. When a cluster is paused, not all functionality will be limited, including the execution of BPMN timers and BPMN message catch events.
-:::
diff --git a/versioned_docs/version-8.5/components/concepts/clusters.md b/versioned_docs/version-8.5/components/concepts/clusters.md
@@ -71,7 +71,3 @@ Additionally in the Starter Plan, the following applies to **development cluster
 
 - **Cluster is not highly available & includes less hardware**: Reduced hardware resources and availability compared to production cluster (for example, one Zeebe node only).
 - **Shorter history of processes and decisions**: Data retention in Operate, Optimize, and Tasklist is reduced to one day. For example, pending or historical process instances are deleted after one day as per the [fair usage limits of the Starter plan](https://camunda.com/legal/fair-usage-limits-for-starter-plan/).
-
-:::caution
-**Cluster auto-pause** is not yet available and only applies to non-Enterprise clusters. Development clusters will be paused if they go unused for two hours. When a cluster is paused, not all functionality is limited. For example, you may still execute BPMN timers and BPMN message catch events. To resume your cluster, review [how to resume a cluster](/components/console/manage-clusters/manage-cluster.md#resume-a-cluster).
-:::
diff --git a/...d_docs/version-8.5/components/console/manage-clusters/create-cluster-include.md b/...d_docs/version-8.5/components/console/manage-clusters/create-cluster-include.md
@@ -48,7 +48,3 @@ Users without **Admin** roles can deploy only on `dev`, `test`, or `stage` clust
 ![cluster-healthy](./img/cluster-overview-new-cluster-healthy.png)
 
 3. After the cluster is created, click on the cluster name to visit the cluster detail page.
-
-:::note
-**Cluster auto-pause** is not yet available and only applies to non-Enterprise clusters. Development clusters will be paused if they go unused for two hours. When a cluster is paused, not all functionality is limited. For example, you may still execute BPMN timers and BPMN message catch events. To resume your cluster, review [how to resume a cluster](/components/console/manage-clusters/manage-cluster.md#resume-a-cluster).
-:::
diff --git a/versioned_docs/version-8.5/components/console/manage-clusters/manage-cluster.md b/versioned_docs/version-8.5/components/console/manage-clusters/manage-cluster.md
@@ -18,10 +18,6 @@ A cluster can be renamed at any time. To rename your cluster, follow the steps b
 
 ## Resume a cluster
 
-:::note
-**Cluster auto-pause** is not yet available and only applies to non-Enterprise clusters. Development clusters will be paused if they go unused for two hours. When a cluster is paused, not all functionality is limited. For example, you may still execute BPMN timers and BPMN message catch events. To learn more about automatic cluster pausing on Free Trial plan clusters, see [auto-pause](/components/concepts/clusters.md#auto-pause).
-:::
-
 You can resume your paused cluster during deployment, or from the **Console** at any time.
 
 ### Resume during deployment