From 43a58d734d7118bd529409bc8b39f0d823e28a80 Mon Sep 17 00:00:00 2001
From: Shaun Struwig <41984034+Blargian@users.noreply.github.com>
Date: Tue, 7 Jan 2025 23:16:14 +0100
Subject: [PATCH] Add description of how automatical idling works with RMV and
 S3 Queue

---
 docs/en/cloud/manage/scaling.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/docs/en/cloud/manage/scaling.md b/docs/en/cloud/manage/scaling.md
index ad49cff3642..cd63366bd2e 100644
--- a/docs/en/cloud/manage/scaling.md
+++ b/docs/en/cloud/manage/scaling.md
@@ -86,6 +86,8 @@ In the **Settings** page, you can also choose whether or not to allow automatic
 
 :::note
 In certain special cases, for instance when a service has a high number of parts, the service will not be idled automatically.
+
+The service may enter an idle state where it suspends refreshes of [refreshable materialized views](/docs/en/materialized-view/refreshable-materialized-view), consumption from [S3Queue](/docs/en/engines/table-engines/integrations/s3queue), and scheduling of new merges. Existing merge operations will complete before the service transitions to the idle state. To ensure continuous operation of refreshable materialized views and S3Queue consumption, disable the idle state functionality.
 :::
 
 :::danger When not to use automatic idling