diff --git a/develop-docs/sdk/telemetry/check-ins.mdx b/develop-docs/sdk/telemetry/check-ins.mdx
index cf98d33099a72..dbffb6f8a6aa7 100644
--- a/develop-docs/sdk/telemetry/check-ins.mdx
+++ b/develop-docs/sdk/telemetry/check-ins.mdx
@@ -221,7 +221,7 @@ When included, the `monitor_config` object supports the following fields:
 |-------|------|----------|-------|-------------|
 | `schedule` | Object | **REQUIRED** | 1.1.0 | Schedule configuration. See [Schedule Configuration](#schedule-configuration). |
 | `checkin_margin` | Number | **OPTIONAL** | 1.1.0 | Allowed margin in minutes after the expected check-in time before the monitor is considered missed. |
-| `max_runtime` | Number | **OPTIONAL** | 1.1.0 | Allowed duration in minutes that a monitor may be `in_progress` before being considered failed due to timeout. |
+| `max_runtime` | Number | **OPTIONAL** | 1.1.0 | Allowed duration in minutes that a monitor may be `in_progress` before being considered failed due to timeout. The maximum is 10080 (7 days); Sentry clamps larger values sent in a monitor upsert. A check-in can stay in progress for at most 7 days, including repeated `in_progress` check-ins. |
 | `failure_issue_threshold` | Number | **OPTIONAL** | 1.4.0 | Number of consecutive failed check-ins before an issue is created. |
 | `recovery_threshold` | Number | **OPTIONAL** | 1.4.0 | Number of consecutive OK check-ins before an issue is resolved. |
 | `timezone` | String | **OPTIONAL** | 1.1.0 | A [tz database](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones) string for the monitor's execution schedule timezone. |
diff --git a/docs/platforms/javascript/common/crons/index.mdx b/docs/platforms/javascript/common/crons/index.mdx
index 2c6cb8a288335..d66ae19055ebd 100644
--- a/docs/platforms/javascript/common/crons/index.mdx
+++ b/docs/platforms/javascript/common/crons/index.mdx
@@ -162,7 +162,7 @@ We recommend that your check-in margin be less than or equal to your interval.
 
 `max_runtime`:
 
-The amount of time (in minutes) your job is allowed to run before it's considered failed. Optional.
+The amount of time (in minutes) your job is allowed to run before it's considered failed. The maximum is 10080 minutes (7 days). Optional.
 
 `failure_issue_threshold`:
 
diff --git a/docs/product/monitors-and-alerts/monitors/crons/getting-started/http/index.mdx b/docs/product/monitors-and-alerts/monitors/crons/getting-started/http/index.mdx
index f87c0608e0e55..894ef770d000a 100644
--- a/docs/product/monitors-and-alerts/monitors/crons/getting-started/http/index.mdx
+++ b/docs/product/monitors-and-alerts/monitors/crons/getting-started/http/index.mdx
@@ -148,7 +148,7 @@ We recommend that your check-in margin be less than or equal to your interval.
 
 `max_runtime`:
 
-The amount of time (in minutes) your job is allowed to run before it's considered failed. Optional.
+The amount of time (in minutes) your job is allowed to run before it's considered failed. The maximum is 10080 minutes (7 days). A check-in can stay in progress for at most 7 days, including repeated in-progress check-ins. Optional.
 
 `failure_issue_threshold`:
 
diff --git a/includes/javascript-crons-upsert.mdx b/includes/javascript-crons-upsert.mdx
index 4ea6d173c1bc1..81cc9d5c1cb42 100644
--- a/includes/javascript-crons-upsert.mdx
+++ b/includes/javascript-crons-upsert.mdx
@@ -85,7 +85,7 @@ We recommend that your check-in margin be less than or equal to your interval.
 
 `maxRuntime`:
 
-The amount of time (in minutes) your job is allowed to run before it's considered failed. Optional.
+The amount of time (in minutes) your job is allowed to run before it's considered failed. The maximum is 10080 minutes (7 days). Optional.
 
 `timezone`: