Skip to content

docs(crons): Document 7 day max_runtime limit #19815

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
wedamija merged 2 commits into from
Oct 5, 2026
Merged

docs(crons): Document 7 day max_runtime limit #19815

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
12a190d
docs(crons): Document 7 day max_runtime limit
wedamija Oct 5, 2026
b8aeb3b
docs(crons): Document 7 day check-in open limit
wedamija Oct 5, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion develop-docs/sdk/telemetry/check-ins.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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. |
Expand Down
2 changes: 1 addition & 1 deletion docs/platforms/javascript/common/crons/index.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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`:

Expand Down
2 changes: 1 addition & 1 deletion docs/product/monitors-and-alerts/monitors/crons/getting-started/http/index.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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`:

Expand Down
2 changes: 1 addition & 1 deletion includes/javascript-crons-upsert.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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`:

Expand Down
Loading