From 7bf100a7114dd6a8c19c7621972d7d7456fa748a Mon Sep 17 00:00:00 2001 From: Hannes Lenke Date: Sun, 8 Nov 2026 06:04:56 -0500 Subject: [PATCH 1/3] docs: explain when Browser checks and Playwright Check Suites keep traces and videos Add a troubleshooting entry for missing traces and videos in Browser checks, correct the Playwright Check Suite trace default (on-first-retry, retention follows use.trace), and say Browser checks record one video per page. Co-Authored-By: Claude Opus 5.5 --- .../browser-checks/playwright-support.mdx | 2 +- .../browser-checks/troubleshooting.mdx | 11 +++++++++++ .../playwright-checks/configuration.mdx | 4 +++- 3 files changed, 15 insertions(+), 2 deletions(-) diff --git a/detect/synthetic-monitoring/browser-checks/playwright-support.mdx b/detect/synthetic-monitoring/browser-checks/playwright-support.mdx index bbaf20e66..6a460f06c 100644 --- a/detect/synthetic-monitoring/browser-checks/playwright-support.mdx +++ b/detect/synthetic-monitoring/browser-checks/playwright-support.mdx @@ -142,7 +142,7 @@ When running tests from the editor page, trace files are always available for do regardless of whether the check is passing or failing. For scheduled check runs traces are only preserved when the check failed. ## Video recordings -When a `@playwright/test` test case fails, Checkly will record a video for each page navigation and make it available in the UI. It is a great tool to get a first look of the actions and their outcome to quickly identify what failed, and to visualize regressions. +When a `@playwright/test` test case fails, Checkly will record a video for each page and make it available in the UI. It is a great tool to get a first look of the actions and their outcome to quickly identify what failed, and to visualize regressions. Here's an example of a Playwright Test script that fails, and provides a video of the test sequence. diff --git a/detect/synthetic-monitoring/browser-checks/troubleshooting.mdx b/detect/synthetic-monitoring/browser-checks/troubleshooting.mdx index 6d33f46a5..bb64a95b0 100644 --- a/detect/synthetic-monitoring/browser-checks/troubleshooting.mdx +++ b/detect/synthetic-monitoring/browser-checks/troubleshooting.mdx @@ -49,6 +49,17 @@ canonical: 'https://www.checklyhq.com/docs/detect/synthetic-monitoring/browser-c 3. Use parallel execution where possible 4. Monitor and alert on performance degradation + + + +**Issue: A result has no trace or video, or some pages have no video** + +**Solutions**: +1. Check whether the run failed. Scheduled runs keep the trace and video only when the check fails. Runs from the editor keep them whether the check passes or fails. See [Viewing trace files](/detect/synthetic-monitoring/browser-checks/playwright-support#viewing-trace-files). +2. Don't rely on the `trace` and `video` options in your Playwright configuration. Browser checks ignore them, so you can't keep artifacts for passing scheduled runs or turn off video recording. To control them, use a [Playwright Check Suite](/detect/synthetic-monitoring/playwright-checks/overview) and [set `use.trace` and `use.video`](/detect/synthetic-monitoring/playwright-checks/configuration#checkly-applied-playwright-settings). +3. Open pages from the test's own `page` or `context` fixture. Playwright records one video per page in that context. Pages from a context you create with `browser.newContext()` have no video. See Playwright's [videos guide](https://playwright.dev/docs/videos). +4. Set a test timeout below the 240-second run limit, for example `test.setTimeout(210000)`. A test that times out on its own test timeout keeps its trace and video. A test still running when the check reaches the run limit is stopped without them. See [Browser check timeouts](/detect/synthetic-monitoring/browser-checks/timeouts). + ## Error Handling and Debugging diff --git a/detect/synthetic-monitoring/playwright-checks/configuration.mdx b/detect/synthetic-monitoring/playwright-checks/configuration.mdx index 54a0ed107..a6d0db96e 100644 --- a/detect/synthetic-monitoring/playwright-checks/configuration.mdx +++ b/detect/synthetic-monitoring/playwright-checks/configuration.mdx @@ -121,16 +121,18 @@ Checkly applies these defaults only when you do not set the option yourself: |-------------------|-----------------| | `workers` | `4` | | `retries` | `2` | +| `use.trace` | `on-first-retry` | | `use.video` | `on-first-retry` | | `use.screenshot` | `on-first-retry` | Your Playwright config or `testCommand` value takes precedence for these options. +Checkly always records a trace, and keeps the trace file only when your `use.trace` setting would have produced one. With the defaults, a test that passes on its first attempt keeps no trace or video, and a failing test keeps them only for its first retry. With `retries` set to `0`, a failing test keeps neither. To keep them for every run, set `use.trace` and `use.video` to `on`. To turn off video recording, set `use.video` to `off`. + Checkly enforces these options for every run. User configuration does not override them: | Playwright setting | Checkly behavior | |--------------------|------------------| -| `use.trace` | `on` for every run | | User agent | Checkly appends a [user-agent suffix](/platform/allowlisting-traffic#default-checkly-user-agent) | Checkly supports Playwright's [`globalTimeout`](https://playwright.dev/docs/api/class-testconfig#test-config-global-timeout). Use it to control the maximum duration of the Playwright suite after `npx playwright test` starts. From 90625859787c95e38a8b287705813c431e04da62 Mon Sep 17 00:00:00 2001 From: Hannes Lenke Date: Sun, 8 Nov 2026 19:40:46 -0500 Subject: [PATCH 2/3] docs: CLI recorded runs keep traces and videos; use the real 240s timeout message Tested on a production account: a passing Browser check run with checkly test --record and checkly trigger --record keeps video and trace. A run past 240 s fails with 'Timed out waiting 240s for the test suite to run'. Co-Authored-By: Claude Opus 5.5 --- detect/synthetic-monitoring/browser-checks/timeouts.mdx | 4 ++-- .../synthetic-monitoring/browser-checks/troubleshooting.mdx | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/detect/synthetic-monitoring/browser-checks/timeouts.mdx b/detect/synthetic-monitoring/browser-checks/timeouts.mdx index f0023cfd7..23a0bcd7d 100644 --- a/detect/synthetic-monitoring/browser-checks/timeouts.mdx +++ b/detect/synthetic-monitoring/browser-checks/timeouts.mdx @@ -61,10 +61,10 @@ test('add item to wishlist', async ({ page }) => { -### Your check run has reached the maximum run time of 240000 ms. +### Timed out waiting 240s for the test suite to run In this case, your script is hitting Checkly's 240s total Browser check timeout. This can't be configured and is in -place to prevent checks from running way longer than acceptable. No assets will be available for review after the check has gone over the maximum run time. If you encounter this, try to make your check shorter by following [best practices](/learn/playwright/writing-tests/). Additionally, to ensure your assets are saved, please set a test timeout lower than the Browser check execution timeout. +place to prevent checks from running way longer than acceptable. The test that was still running at the limit has no trace or video. If you encounter this, try to make your check shorter by following [best practices](/learn/playwright/writing-tests/). Additionally, to ensure your assets are saved, please set a test timeout lower than the Browser check execution timeout. ### Timeout 20000ms exceeded diff --git a/detect/synthetic-monitoring/browser-checks/troubleshooting.mdx b/detect/synthetic-monitoring/browser-checks/troubleshooting.mdx index bb64a95b0..2f98ff082 100644 --- a/detect/synthetic-monitoring/browser-checks/troubleshooting.mdx +++ b/detect/synthetic-monitoring/browser-checks/troubleshooting.mdx @@ -55,7 +55,7 @@ canonical: 'https://www.checklyhq.com/docs/detect/synthetic-monitoring/browser-c **Issue: A result has no trace or video, or some pages have no video** **Solutions**: -1. Check whether the run failed. Scheduled runs keep the trace and video only when the check fails. Runs from the editor keep them whether the check passes or fails. See [Viewing trace files](/detect/synthetic-monitoring/browser-checks/playwright-support#viewing-trace-files). +1. Check whether the run failed. Scheduled runs keep the trace and video only when the check fails. Runs from the editor keep them whether the check passes or fails, and so do runs you record with `npx checkly test --record` or `npx checkly trigger --record`. See [Viewing trace files](/detect/synthetic-monitoring/browser-checks/playwright-support#viewing-trace-files). 2. Don't rely on the `trace` and `video` options in your Playwright configuration. Browser checks ignore them, so you can't keep artifacts for passing scheduled runs or turn off video recording. To control them, use a [Playwright Check Suite](/detect/synthetic-monitoring/playwright-checks/overview) and [set `use.trace` and `use.video`](/detect/synthetic-monitoring/playwright-checks/configuration#checkly-applied-playwright-settings). 3. Open pages from the test's own `page` or `context` fixture. Playwright records one video per page in that context. Pages from a context you create with `browser.newContext()` have no video. See Playwright's [videos guide](https://playwright.dev/docs/videos). 4. Set a test timeout below the 240-second run limit, for example `test.setTimeout(210000)`. A test that times out on its own test timeout keeps its trace and video. A test still running when the check reaches the run limit is stopped without them. See [Browser check timeouts](/detect/synthetic-monitoring/browser-checks/timeouts). From 6c06908edfa495601cbe1932efefddc397b5719c Mon Sep 17 00:00:00 2001 From: Hannes Lenke Date: Mon, 9 Nov 2026 20:07:27 -0500 Subject: [PATCH 3/3] Apply suggestion from @hlenke --- detect/synthetic-monitoring/browser-checks/timeouts.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/detect/synthetic-monitoring/browser-checks/timeouts.mdx b/detect/synthetic-monitoring/browser-checks/timeouts.mdx index 23a0bcd7d..0618f6c66 100644 --- a/detect/synthetic-monitoring/browser-checks/timeouts.mdx +++ b/detect/synthetic-monitoring/browser-checks/timeouts.mdx @@ -64,7 +64,7 @@ test('add item to wishlist', async ({ page }) => { ### Timed out waiting 240s for the test suite to run In this case, your script is hitting Checkly's 240s total Browser check timeout. This can't be configured and is in -place to prevent checks from running way longer than acceptable. The test that was still running at the limit has no trace or video. If you encounter this, try to make your check shorter by following [best practices](/learn/playwright/writing-tests/). Additionally, to ensure your assets are saved, please set a test timeout lower than the Browser check execution timeout. +place to prevent checks from running way longer than acceptable. The test that was still running at the limit has no trace or video. If you encounter this, try to make your check shorter by following [best practices](/learn/playwright/writing-tests/). Additionally, to ensure your assets are saved, please set a test timeout lower than the Browser check execution timeout. Scripts that don't use `@playwright/test` report this limit as `Your check run has reached the maximum run time of 240000 ms.` ### Timeout 20000ms exceeded