From e6d9e57f4931fb47eceb9b64905c6833a955559f Mon Sep 17 00:00:00 2001 From: Hannes Lenke Date: Fri, 6 Nov 2026 21:27:08 -0500 Subject: [PATCH 1/3] docs: say which uptime monitor options depend on your plan Fixed, Linear and Exponential retries and parallel scheduling for uptime monitors aren't on every plan. Mark the options on each uptime monitor page and on the shared retries and scheduling pages, and link pricing. Also fixes "three" retry strategies (there are four). Co-Authored-By: Claude Opus 5.5 --- communicate/alerts/retries.mdx | 4 +++- concepts/scheduling.mdx | 2 ++ detect/uptime-monitoring/dns-monitors/configuration.mdx | 4 ++-- detect/uptime-monitoring/grpc-monitors/configuration.mdx | 4 ++-- detect/uptime-monitoring/icmp-monitors/configuration.mdx | 4 ++-- detect/uptime-monitoring/ssl-monitors/configuration.mdx | 4 ++-- detect/uptime-monitoring/tcp-monitors/configuration.mdx | 4 ++-- detect/uptime-monitoring/tcp-monitors/quickstart.mdx | 4 ++-- .../uptime-monitoring/traceroute-monitors/configuration.mdx | 4 ++-- detect/uptime-monitoring/url-monitors/configuration.mdx | 6 +++++- detect/uptime-monitoring/url-monitors/quickstart.mdx | 4 ++-- 11 files changed, 26 insertions(+), 18 deletions(-) diff --git a/communicate/alerts/retries.mdx b/communicate/alerts/retries.mdx index 2b2240eba..81fd228d9 100644 --- a/communicate/alerts/retries.mdx +++ b/communicate/alerts/retries.mdx @@ -28,13 +28,15 @@ Click **Edit check** or **Edit group** on the 3-dot menu on your [Checkly Home p ### Scheduled check retries -There are three distinct retry strategies based on the time between retry attempts, and each one comes with different retry/backoff characteristics. +There are four retry strategies based on the time between retry attempts, and each one comes with different retry/backoff characteristics. - **Single** — retry once after a fixed interval, e.g. 5s. - **Fixed** — a fixed time between retries, e.g. 5s, 5s, 5s etc. - **Linear** — a linearly increasing time between retries, e.g. 5s, 10s, 15s etc. - **Exponential** — an exponentially increasing time between retries, e.g. 5s, 25s, 125s (2m and 5s) etc. +For uptime monitors, the strategies you can use depend on your [plan](https://www.checklyhq.com/pricing/): **Fixed**, **Linear** and **Exponential** aren't available on every plan. + On top of the time between attempts, you can also set: - **maximum number of retries** - the maximum number of retries for this check or check group. diff --git a/concepts/scheduling.mdx b/concepts/scheduling.mdx index 738f48978..c8f757fa3 100644 --- a/concepts/scheduling.mdx +++ b/concepts/scheduling.mdx @@ -23,6 +23,8 @@ With **Parallel Scheduling**, each time the check is scheduled it will run once Use **Parallel Scheduling** to reduce detection times for regional outages and reduce time to detect service degradations that impact the customer experience. +For uptime monitors, parallel scheduling depends on your [plan](https://www.checklyhq.com/pricing/). + ## How scheduling works Checkly runs each check on a fixed interval, its frequency, not at specific clock times. Frequencies range from every 10 seconds to every 24 hours, depending on the check type. Cron expressions and time-of-day schedules such as "every day at 1:00 AM" are not supported. diff --git a/detect/uptime-monitoring/dns-monitors/configuration.mdx b/detect/uptime-monitoring/dns-monitors/configuration.mdx index f03dc5317..f0100c683 100644 --- a/detect/uptime-monitoring/dns-monitors/configuration.mdx +++ b/detect/uptime-monitoring/dns-monitors/configuration.mdx @@ -352,7 +352,7 @@ Set how often the monitor runs (every 10 seconds to 24 hours): DNS monitor scheduling strategy and location selection interface -* **Strategy:** Choose between round-robin or parallel execution. Learn more about [scheduling strategies](/concepts/scheduling) +* **Strategy:** Choose between round-robin or parallel execution. Learn more about [scheduling strategies](/concepts/scheduling). Parallel scheduling depends on your [plan](https://www.checklyhq.com/pricing/). * **Locations:** Select [public](/concepts/locations/#public-locations) or [private](/platform/private-locations/overview) locations to run the monitor from ### Additional Settings @@ -360,7 +360,7 @@ Set how often the monitor runs (every 10 seconds to 24 hours): * **Name:** Give your monitor a clear name to identify it in dashboards and alerts * **Description:** Add context about what this monitor does and why it matters. Supports markdown, max 500 characters. When a failure occurs, [Rocky AI](/ai/rocky-ai) uses the description to provide more accurate [root cause and user impact analysis](/resolve/ai-root-cause-analysis/overview) * **Tags:** Use tags to organize monitors across [dashboards](/communicate/dashboards/overview/) and [maintenance windows](/communicate/maintenance-windows/overview) -* **Retries:** Define how failed runs should be retried. See [retry strategies](/communicate/alerts/retries) +* **Retries:** Define how failed runs should be retried. See [retry strategies](/communicate/alerts/retries). Which retry strategies you can use depends on your [plan](https://www.checklyhq.com/pricing/). * **Alerting:** Configure your [alert settings](/communicate/alerts/configuration), [alert channels](/communicate/alerts/channels), or set up [webhooks](/integrations/alerts/webhooks) for custom integrations ## Common Use Cases diff --git a/detect/uptime-monitoring/grpc-monitors/configuration.mdx b/detect/uptime-monitoring/grpc-monitors/configuration.mdx index 1215de66e..d509a995f 100644 --- a/detect/uptime-monitoring/grpc-monitors/configuration.mdx +++ b/detect/uptime-monitoring/grpc-monitors/configuration.mdx @@ -76,7 +76,7 @@ Set how often the monitor runs (every 10 seconds to 24 hours). ### Scheduling & Locations -* **Strategy**: Choose between round-robin or parallel execution. Learn more about [scheduling strategies](/concepts/scheduling) +* **Strategy**: Choose between round-robin or parallel execution. Learn more about [scheduling strategies](/concepts/scheduling). Parallel scheduling depends on your [plan](https://www.checklyhq.com/pricing/). * **Locations**: Select [public](/concepts/locations/#public-locations) or [private](/platform/private-locations/overview) locations to run the monitor from ### Additional Settings @@ -84,5 +84,5 @@ Set how often the monitor runs (every 10 seconds to 24 hours). * **Name**: Give your monitor a clear name to identify it in dashboards and alerts * **Description**: Add context about what this monitor does and why it matters. Supports markdown, max 500 characters. When a failure occurs, [Rocky AI](/ai/rocky-ai) uses the description to provide more accurate [root cause and user impact analysis](/resolve/ai-root-cause-analysis/overview) * **Tags**: Use tags to organize monitors across [dashboards](/communicate/dashboards/overview/) and [maintenance windows](/communicate/maintenance-windows/overview) -* **Retries**: Define how failed runs should be retried. See [retry strategies](/communicate/alerts/retries) +* **Retries**: Define how failed runs should be retried. See [retry strategies](/communicate/alerts/retries). Which retry strategies you can use depends on your [plan](https://www.checklyhq.com/pricing/). * **Alerting**: Configure your [alert settings](/communicate/alerts/configuration), [alert channels](/communicate/alerts/channels), or set up [webhooks](/integrations/alerts/webhooks) for custom integrations diff --git a/detect/uptime-monitoring/icmp-monitors/configuration.mdx b/detect/uptime-monitoring/icmp-monitors/configuration.mdx index 514b42034..bf5544d3c 100644 --- a/detect/uptime-monitoring/icmp-monitors/configuration.mdx +++ b/detect/uptime-monitoring/icmp-monitors/configuration.mdx @@ -96,7 +96,7 @@ Set how often the monitor runs (every 10 seconds to 24 hours): ICMP monitor scheduling strategy and location selection interface -* **Strategy:** Choose between round-robin or parallel execution. Learn more about [scheduling strategies](/concepts/scheduling) +* **Strategy:** Choose between round-robin or parallel execution. Learn more about [scheduling strategies](/concepts/scheduling). Parallel scheduling depends on your [plan](https://www.checklyhq.com/pricing/). * **Locations:** Select [public](/concepts/locations/#public-locations) or [private](/platform/private-locations/overview) locations to run the monitor from ### Additional Settings @@ -104,7 +104,7 @@ Set how often the monitor runs (every 10 seconds to 24 hours): * **Name:** Give your monitor a clear name to identify it in dashboards and alerts * **Description:** Add context about what this monitor does and why it matters. Supports markdown, max 500 characters. When a failure occurs, [Rocky AI](/ai/rocky-ai) uses the description to provide more accurate [root cause and user impact analysis](/resolve/ai-root-cause-analysis/overview) * **Tags:** Use tags to organize monitors across [dashboards](/communicate/dashboards/overview/) and [maintenance windows](/communicate/maintenance-windows/overview) -* **Retries:** Define how failed runs should be retried. See [retry strategies](/communicate/alerts/retries) +* **Retries:** Define how failed runs should be retried. See [retry strategies](/communicate/alerts/retries). Which retry strategies you can use depends on your [plan](https://www.checklyhq.com/pricing/). * **Alerting:** Configure your [alert settings](/communicate/alerts/configuration), [alert channels](/communicate/alerts/channels), or set up [webhooks](/integrations/alerts/webhooks) for custom integrations diff --git a/detect/uptime-monitoring/ssl-monitors/configuration.mdx b/detect/uptime-monitoring/ssl-monitors/configuration.mdx index 490e54495..5f888018e 100644 --- a/detect/uptime-monitoring/ssl-monitors/configuration.mdx +++ b/detect/uptime-monitoring/ssl-monitors/configuration.mdx @@ -139,7 +139,7 @@ Set how often the monitor runs. SSL monitors run at most **once per minute** (ev ### Scheduling & Locations -* **Strategy:** Choose between round-robin or parallel execution. Learn more about [scheduling strategies](/concepts/scheduling). +* **Strategy:** Choose between round-robin or parallel execution. Learn more about [scheduling strategies](/concepts/scheduling). Parallel scheduling depends on your [plan](https://www.checklyhq.com/pricing/). * **Locations:** Select [public](/concepts/locations/#public-locations) or [private](/platform/private-locations/overview) locations to run the monitor from. ### Additional Settings @@ -147,5 +147,5 @@ Set how often the monitor runs. SSL monitors run at most **once per minute** (ev * **Name:** Give your monitor a clear name to identify it in dashboards and alerts. * **Description:** Add context about what this monitor does and why it matters. Supports markdown, max 500 characters. When a failure occurs, [Rocky AI](/ai/rocky-ai) uses the description to provide more accurate [root cause and user impact analysis](/resolve/ai-root-cause-analysis/overview). * **Tags:** Use tags to organize monitors across [dashboards](/communicate/dashboards/overview/) and [maintenance windows](/communicate/maintenance-windows/overview). -* **Retries:** Define how failed runs should be retried. See [retry strategies](/communicate/alerts/retries). +* **Retries:** Define how failed runs should be retried. See [retry strategies](/communicate/alerts/retries). Which retry strategies you can use depends on your [plan](https://www.checklyhq.com/pricing/). * **Alerting:** Configure your [alert settings](/communicate/alerts/configuration), [alert channels](/communicate/alerts/channels), or set up [webhooks](/integrations/alerts/webhooks) for custom integrations. diff --git a/detect/uptime-monitoring/tcp-monitors/configuration.mdx b/detect/uptime-monitoring/tcp-monitors/configuration.mdx index 5925e19e4..526b9f87c 100644 --- a/detect/uptime-monitoring/tcp-monitors/configuration.mdx +++ b/detect/uptime-monitoring/tcp-monitors/configuration.mdx @@ -62,7 +62,7 @@ Set how often the monitor runs (every 10 seconds to 24 hours). Sub-minute freque TCP monitor scheduling strategy and location selection interface -* **Strategy:** Choose between round-robin or parallel execution. Learn more about [scheduling strategies](/concepts/scheduling) +* **Strategy:** Choose between round-robin or parallel execution. Learn more about [scheduling strategies](/concepts/scheduling). Parallel scheduling depends on your [plan](https://www.checklyhq.com/pricing/). * **Locations:** Select [public](/concepts/locations/#public-locations) or [private](/platform/private-locations/overview) locations to run the monitor from ### Additional Settings @@ -70,7 +70,7 @@ Set how often the monitor runs (every 10 seconds to 24 hours). Sub-minute freque * **Name:** Give your monitor a clear name to identify it in dashboards and alerts * **Description:** Add context about what this monitor does and why it matters. Supports markdown, max 500 characters. When a failure occurs, [Rocky AI](/ai/rocky-ai) uses the description to provide more accurate [root cause and user impact analysis](/resolve/ai-root-cause-analysis/overview) * **Tags:** Use tags to organize monitors across dashboards and [maintenance windows](/communicate/maintenance-windows/overview) -* **Retries:** Define how failed runs should be retried. See [retry strategies](/communicate/alerts/retries) +* **Retries:** Define how failed runs should be retried. See [retry strategies](/communicate/alerts/retries). Which retry strategies you can use depends on your [plan](https://www.checklyhq.com/pricing/). * **Alerting:** Configure your [alert settings](/communicate/alerts/configuration), [alert channels](/communicate/alerts/channels), or set up [webhooks](/integrations/alerts/webhooks) for custom integrations diff --git a/detect/uptime-monitoring/tcp-monitors/quickstart.mdx b/detect/uptime-monitoring/tcp-monitors/quickstart.mdx index 1d4700c61..2ca185131 100644 --- a/detect/uptime-monitoring/tcp-monitors/quickstart.mdx +++ b/detect/uptime-monitoring/tcp-monitors/quickstart.mdx @@ -60,7 +60,7 @@ Set how often the monitor runs (every 10 seconds to 24 hours): TCP monitor scheduling strategy and location selection interface -* **Strategy:** Choose between round-robin or parallel execution. Learn more about [scheduling strategies](/concepts/scheduling#scheduling-strategies) +* **Strategy:** Choose between round-robin or parallel execution. Learn more about [scheduling strategies](/concepts/scheduling#scheduling-strategies). Parallel scheduling depends on your [plan](https://www.checklyhq.com/pricing/). * **Locations:** Select [public](/concepts/locations) or [private](/platform/private-locations/overview) locations to run the monitor from ## Additional Settings @@ -68,7 +68,7 @@ Set how often the monitor runs (every 10 seconds to 24 hours): * **Name:** Give your monitor a clear name to identify it in dashboards and alerts * **Tags:** Use tags to organize monitors across dashboards and [maintenance windows](/communicate/maintenance-windows/overview) * **Description:** A description of the check. Supports Markdown. Maximum length: 500 characters -* **Retries:** Define how failed runs should be retried. See [retry strategies](/communicate/alerts/retries) +* **Retries:** Define how failed runs should be retried. See [retry strategies](/communicate/alerts/retries). Which retry strategies you can use depends on your [plan](https://www.checklyhq.com/pricing/). * **Alerting:** Configure your [alert settings](/communicate/alerts/configuration), [alert channels](/communicate/alerts/channels), or set up [webhooks](/integrations/alerts/webhooks) for custom integrations diff --git a/detect/uptime-monitoring/traceroute-monitors/configuration.mdx b/detect/uptime-monitoring/traceroute-monitors/configuration.mdx index 7830d9244..f16793450 100644 --- a/detect/uptime-monitoring/traceroute-monitors/configuration.mdx +++ b/detect/uptime-monitoring/traceroute-monitors/configuration.mdx @@ -100,7 +100,7 @@ Set how often the monitor runs. Traceroute monitors run at most **once every 30 ### Scheduling & Locations -* **Strategy:** Choose between round-robin or parallel execution. Learn more about [scheduling strategies](/concepts/scheduling) +* **Strategy:** Choose between round-robin or parallel execution. Learn more about [scheduling strategies](/concepts/scheduling). Parallel scheduling depends on your [plan](https://www.checklyhq.com/pricing/). * **Locations:** Select [public](/concepts/locations/#public-locations) or [private](/platform/private-locations/overview) locations to run the monitor from ### Additional Settings @@ -108,5 +108,5 @@ Set how often the monitor runs. Traceroute monitors run at most **once every 30 * **Name:** Give your monitor a clear name to identify it in dashboards and alerts * **Description:** Add context about what this monitor does and why it matters. Supports markdown, max 500 characters. When a failure occurs, [Rocky AI](/ai/rocky-ai) uses the description to provide more accurate [root cause and user impact analysis](/resolve/ai-root-cause-analysis/overview) * **Tags:** Use tags to organize monitors across [dashboards](/communicate/dashboards/overview/) and [maintenance windows](/communicate/maintenance-windows/overview) -* **Retries:** Define how failed runs should be retried. See [retry strategies](/communicate/alerts/retries) +* **Retries:** Define how failed runs should be retried. See [retry strategies](/communicate/alerts/retries). Which retry strategies you can use depends on your [plan](https://www.checklyhq.com/pricing/). * **Alerting:** Configure your [alert settings](/communicate/alerts/configuration), [alert channels](/communicate/alerts/channels), or set up [webhooks](/integrations/alerts/webhooks) for custom integrations diff --git a/detect/uptime-monitoring/url-monitors/configuration.mdx b/detect/uptime-monitoring/url-monitors/configuration.mdx index 2a7095a04..08fc8f0a8 100644 --- a/detect/uptime-monitoring/url-monitors/configuration.mdx +++ b/detect/uptime-monitoring/url-monitors/configuration.mdx @@ -62,7 +62,7 @@ Choose when and how your checks run across multiple locations: * **Round Robin** (Default): Checks run on one of the selected locations each time it is scheduled -* **Parallel**: Checks run from all selected locations simultaneously. Higher consumption but provides immediate global visibility for critical services +* **Parallel**: Checks run from all selected locations simultaneously. Higher consumption but provides immediate global visibility for critical services. Available depending on your [plan](https://www.checklyhq.com/pricing/) Learn more in our documentation on [Scheduling strategies](/concepts/scheduling/#scheduling-strategies). @@ -92,6 +92,10 @@ Select the retry strategy to determine how failed checks are retried: | **Linear** | Increase retry delay linearly with each attempt to avoid overwhelming failed services | | **Exponential** | Grow the retry delay exponentially (base delay to the power of the attempt, e.g. 5s, 25s, 125s) for maximum protection against service overload | + +The strategies you can select depend on your [plan](https://www.checklyhq.com/pricing/). Plans without multiple retries for uptime monitors offer **None** and **Single** only; **Fixed**, **Linear** and **Exponential** need a plan that includes them. + + ### Alert Settings Configure notifications for your team: diff --git a/detect/uptime-monitoring/url-monitors/quickstart.mdx b/detect/uptime-monitoring/url-monitors/quickstart.mdx index 6abd5fb53..aca5bc928 100644 --- a/detect/uptime-monitoring/url-monitors/quickstart.mdx +++ b/detect/uptime-monitoring/url-monitors/quickstart.mdx @@ -56,7 +56,7 @@ Set how often the monitor runs (every 10 seconds to 24 hours). URL monitor scheduling strategy interface showing round robin vs fixed schedule options -* **Scheduling:** Choose between round-robin or parallel execution. Learn more about [scheduling strategies](/concepts/scheduling) +* **Scheduling:** Choose between round-robin or parallel execution. Learn more about [scheduling strategies](/concepts/scheduling). Parallel scheduling depends on your [plan](https://www.checklyhq.com/pricing/). * **Locations:** Select [public](/concepts/locations) or [private](/platform/private-locations/overview) locations to run the monitor from ## Additional Settings @@ -64,7 +64,7 @@ Set how often the monitor runs (every 10 seconds to 24 hours). * **Name:** Give your monitor a clear name to identify it in dashboards and alerts * **Tags:** Use tags to organize monitors across dashboards and [maintenance windows](/communicate/maintenance-windows/overview) * **Description:** A short description of the check. Supports Markdown. Maximum length: 500 characters -* **Retries:** Define how failed runs should be retried. See [retry strategies](/communicate/alerts/retries) +* **Retries:** Define how failed runs should be retried. See [retry strategies](/communicate/alerts/retries). Which retry strategies you can use depends on your [plan](https://www.checklyhq.com/pricing/). * **Alerting:** Configure your [alert settings](/communicate/alerts/configuration), [alert channels](/communicate/alerts/channels), or set up [webhooks](/integrations/alerts/webhooks) for custom integrations From 4bbd2b777aa666f2f65f9410796adfc0ff5c62e8 Mon Sep 17 00:00:00 2001 From: Hannes Lenke Date: Sat, 7 Nov 2026 16:00:40 -0500 Subject: [PATCH 2/3] Apply suggestion from @hlenke --- detect/uptime-monitoring/url-monitors/configuration.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/detect/uptime-monitoring/url-monitors/configuration.mdx b/detect/uptime-monitoring/url-monitors/configuration.mdx index 08fc8f0a8..de5345350 100644 --- a/detect/uptime-monitoring/url-monitors/configuration.mdx +++ b/detect/uptime-monitoring/url-monitors/configuration.mdx @@ -62,7 +62,7 @@ Choose when and how your checks run across multiple locations: * **Round Robin** (Default): Checks run on one of the selected locations each time it is scheduled -* **Parallel**: Checks run from all selected locations simultaneously. Higher consumption but provides immediate global visibility for critical services. Available depending on your [plan](https://www.checklyhq.com/pricing/) +* **Parallel**: Checks run from all selected locations simultaneously. Higher consumption but provides immediate global visibility for critical services. Parallel scheduling depends on your [plan](https://www.checklyhq.com/pricing/). Learn more in our documentation on [Scheduling strategies](/concepts/scheduling/#scheduling-strategies). From 5d0a348f989ecb8076f948865c2bc692c04afb83 Mon Sep 17 00:00:00 2001 From: Hannes Lenke Date: Sat, 7 Nov 2026 16:01:11 -0500 Subject: [PATCH 3/3] Apply suggestion from @hlenke --- detect/uptime-monitoring/url-monitors/configuration.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/detect/uptime-monitoring/url-monitors/configuration.mdx b/detect/uptime-monitoring/url-monitors/configuration.mdx index de5345350..4c4382bef 100644 --- a/detect/uptime-monitoring/url-monitors/configuration.mdx +++ b/detect/uptime-monitoring/url-monitors/configuration.mdx @@ -93,7 +93,7 @@ Select the retry strategy to determine how failed checks are retried: | **Exponential** | Grow the retry delay exponentially (base delay to the power of the attempt, e.g. 5s, 25s, 125s) for maximum protection against service overload | -The strategies you can select depend on your [plan](https://www.checklyhq.com/pricing/). Plans without multiple retries for uptime monitors offer **None** and **Single** only; **Fixed**, **Linear** and **Exponential** need a plan that includes them. +Most plans offer **None** and **Single** only. **Fixed**, **Linear** and **Exponential** need a [plan](https://www.checklyhq.com/pricing/) that includes multiple retries for uptime monitors. ### Alert Settings