From 565c81d0c5d7da85a90b6640dd3f7ca3df4bb670 Mon Sep 17 00:00:00 2001 From: Dan Heath <76443935+Dan-Heath@users.noreply.github.com> Date: Fri, 24 Oct 2025 10:56:16 -0400 Subject: [PATCH] Update website/content/docs/session-recording/index.mdx Co-authored-by: Irena Rindos --- website/content/docs/session-recording/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/content/docs/session-recording/index.mdx b/website/content/docs/session-recording/index.mdx index c7e3093e3b..d2b8b2ed1d 100644 --- a/website/content/docs/session-recording/index.mdx +++ b/website/content/docs/session-recording/index.mdx @@ -68,7 +68,7 @@ Determining how much storage you need to allocate on workers and the external st When you estimate worker storage requirements, consider the number of concurrent sessions that will be recorded on that worker. Boundary writes the BSR to the worker's local storage while the session is active, and then moves it to the remote storage bucket when the session is closed. -You use the `recording_storage_minimum_available_capacity` setting to configure how much local disk storage space is available on the worker for the cache. +You use the `recording_storage_minimum_available_capacity` setting to configure the minimum amount of storage space that is required for workers to perform session recording operations. If a worker is at or below the storage threshold, Boundary does not use the worker to record sessions or play back recordings. Boundary determines the worker's local storage state based on the capacity you configure. If the worker falls below the storage threshold, or if it runs out of local disk space, it may impact your ability to record sessions. Refer to [Local storage](/boundary/docs/session-recording/configuration/configure-worker-storage#local-storage) for more information about configuring storage capacity and the possible storage states.