docs(console): Add cluster autopause

docs/components/concepts/clusters.md

@@ -24,12 +24,31 @@ When you deploy and execute your [BPMN](/components/modeler/bpmn/bpmn.md) or [DM
 
 ## Free Trial cluster
 
-Free Trial clusters have the same functionality as a production cluster, but are size small and only available during your trial period. You cannot convert a Free Trial cluster to a different kind of cluster.
+Free Trial clusters have the same functionality as a production cluster, but are size [small (S)](/components/best-practices/architecture/sizing-your-environment.md#camunda-8-saas) and only available during your trial period. You cannot convert a Free Trial cluster to a different kind of cluster.
 
 Once you sign up for a Free Trial, you are able to create one production cluster for the duration of your trial.
 
 When your Free Trial plan expires, you are automatically transferred to the Free Plan. This plan allows you to model BPMN and DMN collaboratively, but does not support execution of your models. Any cluster created during your trial is deleted, and you cannot create new clusters.
 
+### Auto-pause
+
+Free Trial `dev` (or untagged) clusters are automatically paused eight hours after the creation of the cluster or since you last resumed the paused cluster. Auto-pause occurs regardless of cluster usage.
+
+You can resume a paused cluster at any time, which typically takes five to ten minutes to complete. See [resume your cluster](/components/console/manage-clusters/resume-cluster.md/).
+
+- Clusters tagged as `test`, `stage`, or `prod` do not auto-pause.
+- Paused 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.
+
+:::tip
+
+To prevent auto-pause, you can:
+
+- Tag the cluster as `test`, `stage`, or `prod` instead of `dev`.
+- [Upgrade your Free Trial plan](https://camunda.com/pricing/) to a Starter, Professional, or Enterprise plan.
+
+:::
+
 ## Development clusters
 
 Development clusters, available in the Starter and Enterprise plans, are recommended for development, testing, proof of concepts, and demos.
@@ -52,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.
-:::

docs/components/console/manage-clusters/resume-cluster.md

@@ -1,7 +1,17 @@
 ---
 id: resume-cluster
 title: Resume your cluster
-description: "Follow these instructions to resume your cluster"
+description: "You can resume your paused cluster at any time"
 ---
 
-A trial cluster can be paused automatically due to inactivity. To resume your cluster, navigate to the **Clusters** tab, click on the cluster name (e.g. Prod Cluster - Project A) from the list and in the cluster details, and click **Resume cluster**.
+If your cluster is paused, you can resume it at any time.
+
+To resume your paused cluster:
+
+1. Navigate to **Console**, and select the **Clusters** tab.
+1. The cluster **Status** shows “Paused” if a cluster is paused. Select the cluster that you want to resume.
+1. On the cluster **Overview** tab, select **Resume cluster** in the **Status** row of the **Cluster Details**. The cluster resumes running, which typically takes five to ten minutes to complete.
+
+:::info
+To learn more about automatic cluster pausing on Free Trial plan clusters, see [auto-pause](/components/concepts/clusters.md#auto-pause).
+:::