From f0debe9be8e24590210d59ef385f5fa5cca9ad7a Mon Sep 17 00:00:00 2001
From: ANSHSINGH050404 <114014895+ANSHSINGH050404@users.noreply.github.com>
Date: Mon, 20 Jul 2026 12:25:10 +0530
Subject: [PATCH] docs: clarify FROZEN is the legacy name for WAITING run
 status

Closes #2279
---
 docs/runs.mdx | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/docs/runs.mdx b/docs/runs.mdx
index 4a4b301b309..10cc4180298 100644
--- a/docs/runs.mdx
+++ b/docs/runs.mdx
@@ -45,6 +45,13 @@ currently being executed by a worker.
 <Icon icon="hourglass" iconType="solid" color="#878C99" size={17} /> **Waiting**: You have used a
 [triggerAndWait()](/triggering#yourtask-triggerandwait), [batchTriggerAndWait()](/triggering#yourtask-batchtriggerandwait) or a [wait function](/wait). When the wait is complete, the task will resume execution.
 
+<Note>
+  Older API versions may report this state as **`FROZEN`**. Current API versions map the same
+  internal paused/waiting-to-resume states to **`WAITING`**. If you branch on status strings from
+  the API, treat `FROZEN` as equivalent to `WAITING` for compatibility with clients that omit the
+  current API version header.
+</Note>
+
 ### Final states
 
 <Icon icon="circle-check" iconType="solid" color="#28BF5C" size={17} /> **Completed**: The task has successfully