diff --git a/detect/synthetic-monitoring/playwright-checks/configuration.mdx b/detect/synthetic-monitoring/playwright-checks/configuration.mdx
index c5f360ed..15f3af42 100644
--- a/detect/synthetic-monitoring/playwright-checks/configuration.mdx
+++ b/detect/synthetic-monitoring/playwright-checks/configuration.mdx
@@ -239,3 +239,19 @@ If tests fail due to authentication issues:
 
 - Verify environment variables are set correctly in Checkly. You can verify your environment variables using `npx checkly env ls`, or looking at your Global or Check's environment variables in the Checkly Webapp to ensure any `process.env.VARIABLE_NAME` call from your test is defined.
 - For persistent authentication, use Playwright's [`storageState`](https://playwright.dev/docs/auth#reuse-authentication-state) feature.
+
+**webServer configuration requires additional files**
+
+When using `webServer` in your Playwright config, you need to include the server files in your check configuration:
+
+- Add server files to the `include` parameter in your [Playwright check configuration](/constructs/playwright-check/#param-include)
+- Include all files needed to start the server (e.g., server scripts, config files)
+- Alternatively, skip `webServer` on Checkly and use your deployed URL: `...(process.env.CHECKLY ? {} : { webServer: { ... } })`
+
+**No tests found**
+
+If Playwright couldn't find any tests to run, this usually means a mismatch between your config and your test files:
+
+- Verify your `--grep` pattern matches actual test tags or projects
+- Verify the `testDir` path in `playwright.config.ts` matches the actual directory containing your test files
+- Ensure path aliases (`~/`, `@/`) in imports are configured in your `tsconfig.json`, or replace them with relative paths
diff --git a/detect/synthetic-monitoring/playwright-checks/custom-dependencies.mdx b/detect/synthetic-monitoring/playwright-checks/custom-dependencies.mdx
index 1f690d61..2b4c64b3 100644
--- a/detect/synthetic-monitoring/playwright-checks/custom-dependencies.mdx
+++ b/detect/synthetic-monitoring/playwright-checks/custom-dependencies.mdx
@@ -189,4 +189,19 @@ If Checkly uses the wrong package manager:
 If package installation exceeds time limits:
 
 - Check for large dependencies that can be optimized
-- Consider using a custom `installCommand` to install only required packages
\ No newline at end of file
+- Consider using a custom `installCommand` to install only required packages
+
+### Memory usage exceeded
+
+If you see errors indicating that memory limits were exceeded during installation:
+
+- Optimize your dependencies to reduce memory consumption
+- Consider using a custom `installCommand` to install only necessary packages
+
+### General installation failures
+
+If you encounter general installation errors:
+
+- Review the full error logs for specific issues
+- Ensure all dependencies are compatible with the Node.js version used by Checkly
+- Consider using a custom `installCommand` to handle complex installations
\ No newline at end of file
diff --git a/detect/synthetic-monitoring/playwright-checks/timeouts.mdx b/detect/synthetic-monitoring/playwright-checks/timeouts.mdx
index f1ccaa25..aae34449 100644
--- a/detect/synthetic-monitoring/playwright-checks/timeouts.mdx
+++ b/detect/synthetic-monitoring/playwright-checks/timeouts.mdx
@@ -71,6 +71,8 @@ Failed to run install command
 - Check if your registry is slow or has issues
 - Update and commit your lock file
 
+See the [Custom dependencies troubleshooting guide](/detect/synthetic-monitoring/playwright-checks/custom-dependencies#troubleshooting) for more detailed solutions.
+
 ### Global timeout exceeded
 
 ```