From 7d11ea8444626310434109e349864fb4dde4726b Mon Sep 17 00:00:00 2001 From: rca-bot Date: Wed, 24 Jun 2026 15:32:51 +0000 Subject: [PATCH 1/3] fix: clarify private location unavailability detection conditions and timing - Add missing condition: location must be assigned to at least one check for unavailability detection to trigger - Fix timing claim: detection takes up to 20 min (10-min agent window + 10-min cron interval), not exactly 10 min Reported via support ticket IT-1024 / FUN-810. --- platform/private-locations/overview.mdx | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/platform/private-locations/overview.mdx b/platform/private-locations/overview.mdx index 72d9b5dc..785d9a85 100644 --- a/platform/private-locations/overview.mdx +++ b/platform/private-locations/overview.mdx @@ -84,7 +84,9 @@ new ApiCheck('hello-api-1', { ## Unavailable Private Locations -If a private location has had no Checkly agents connected for more than 10 minutes, it will be flagged as unavailable. Checkly will email account owners and admins that the location has become unavailable. +A private location is flagged as unavailable when it is assigned to at least one check and has had no Checkly agents connected for more than 10 minutes. Checkly will email account owners and admins when this happens. + +Detection can take up to 20 minutes in the worst case: the system evaluates agent connectivity every 10 minutes and requires agents to have been absent for the full preceding 10-minute window. While a location is unavailable, no checks will be scheduled to run on it. When a location becomes available, check scheduling and execution will resume automatically. From 1e3a06b6946c90340db68825fca8e10b5d32d125 Mon Sep 17 00:00:00 2001 From: Laura Guo Date: Thu, 25 Jun 2026 09:58:05 -0400 Subject: [PATCH 2/3] Make Angie's edit less verbose --- platform/private-locations/overview.mdx | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/platform/private-locations/overview.mdx b/platform/private-locations/overview.mdx index 785d9a85..2f95f0dc 100644 --- a/platform/private-locations/overview.mdx +++ b/platform/private-locations/overview.mdx @@ -84,9 +84,7 @@ new ApiCheck('hello-api-1', { ## Unavailable Private Locations -A private location is flagged as unavailable when it is assigned to at least one check and has had no Checkly agents connected for more than 10 minutes. Checkly will email account owners and admins when this happens. - -Detection can take up to 20 minutes in the worst case: the system evaluates agent connectivity every 10 minutes and requires agents to have been absent for the full preceding 10-minute window. +If a private location has checks assigned but no Checkly agents connected for more than 20 minutes, it will be flagged as unavailable. Checkly will email account owners and admins when this happens. While a location is unavailable, no checks will be scheduled to run on it. When a location becomes available, check scheduling and execution will resume automatically. From a2d2733787fb0197d72b362e58914a323949437a Mon Sep 17 00:00:00 2001 From: Laura Guo Date: Thu, 25 Jun 2026 09:58:45 -0400 Subject: [PATCH 3/3] Fix broken description YAML in skills/playwright-best-practices-for-agents/SKILL.md --- skills/playwright-best-practices-for-agents/SKILL.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/skills/playwright-best-practices-for-agents/SKILL.md b/skills/playwright-best-practices-for-agents/SKILL.md index 9028860f..ac5e1afe 100644 --- a/skills/playwright-best-practices-for-agents/SKILL.md +++ b/skills/playwright-best-practices-for-agents/SKILL.md @@ -1,6 +1,6 @@ --- name: playwright-best-practices-for-agents -description: Agent-first best practices for writing, structuring, debugging, and stabilizing Playwright tests in TypeScript/JavaScript, built around Playwright's agent CLI (`playwright-cli`) and no-GUI agentic debugging flows. Use when authoring or reviewing Playwright tests: choosing locators, writing web-first assertions, fixing flaky tests, handling authentication (SSO/2FA), mocking network/API requests, structuring projects and fixtures, generating test data, building forms and validation, pressing keys and keyboard shortcuts, hovering and other mouse actions, handling native alert/confirm/prompt dialogs, uploading or downloading files, testing iframes, multiple tabs/popups or multi-user flows, mobile and device emulation, mocking time and dates, visual regression and screenshots, tagging and annotating tests, catching console errors, testing error/offline/loading states, configuring global setup, or running Playwright in CI. +description: "Agent-first best practices for writing, structuring, debugging, and stabilizing Playwright tests in TypeScript/JavaScript, built around Playwright's agent CLI (`playwright-cli`) and no-GUI agentic debugging flows. Use when authoring or reviewing Playwright tests: choosing locators, writing web-first assertions, fixing flaky tests, handling authentication (SSO/2FA), mocking network/API requests, structuring projects and fixtures, generating test data, building forms and validation, pressing keys and keyboard shortcuts, hovering and other mouse actions, handling native alert/confirm/prompt dialogs, uploading or downloading files, testing iframes, multiple tabs/popups or multi-user flows, mobile and device emulation, mocking time and dates, visual regression and screenshots, tagging and annotating tests, catching console errors, testing error/offline/loading states, configuring global setup, or running Playwright in CI." metadata: author: checkly ---