Timeout overview
| Timeout stage | Default timeout | Configurable |
|---|---|---|
| Global Playwright Check Suite timeout | 30 minutes | No |
| Dependency installation | 5 minutes | No |
| Playwright test timeout | Inherits from your config | Yes |
| Playwright navigation timeout | Inherits from your config | Yes |
| Playwright action timeout | Inherits from your config | Yes |
| Artifact upload and secret scrubbing | No timeout | No |
Playwright Check Suite execution stages
When Checkly runs your Playwright Check Suite, it has a global timeout of 30 minutes, while going through these stages:1. Pre-processing
Checkly prepares your execution environment:- Playwright and browsers: Load the right playwright version with its corresponding browsers
- Dependencies cache download: Downloads the dependencies cache if it exists
- Dependency installation: If the dependencies cache doesn’t exist, Checkly runs the install command (default:
npm install,pnpm installoryarn install)- This stage has a 5-minute timeout
- Use
installCommandin your check suite configuration to run a custom dependency installation command. This can help prevent timeouts during installation. For exampleinstallCommand: 'npm install --ignore-scripts'to skip running postinstall and other lifecycle scripts
- Creates and uploads new dependencies cache: This cache will be used in consecutive runs in your account with the same dependencies
2. Test execution
Checkly runs your tests usingnpx playwright test:
- The timeouts of this stage are set through the timeouts in your Playwright tests and configuration.
- To set a global playwright test timeout in Checkly, use a custom test command,
testCommand, in your check suite configuration- Use
testCommand: npx playwright test --global-timeout=<timeout_in_ms>to customize the timeout of this step
- Use
3. Post-processing
After tests complete, Checkly:- Uploads artifacts: Screenshots, videos, traces
- Scrubs secrets: Removes secrets declared in your Checkly Environment Secrets from logs and artifacts
Playwright-specific timeouts
Checkly runs your tests with the timeout configuration from yourplaywright.config.ts and test files. Configure test timeout, navigation timeout, and action timeout according to your needs. See Playwright’s timeout documentation for detailed configuration options.
Troubleshooting timeout-related errors
Dependency installation timeout exceeded
- Reduce dependencies in your
package.json - Remove large or unnecessary packages
- Check if your registry is slow or has issues
- Update and commit your lock file
Global timeout exceeded
- Split tests into multiple check suites using
pwTags,pwProjectsor a customtestCommand.
Playwright test timeout exceeded
Playwright navigation timeout exceeded
page.goto()) took longer than the navigation timeout.
Solution: Increase the navigation timeout in your Playwright configuration or for specific navigation actions. See Playwright’s timeout documentation for configuration options.