Prerequisites
Prerequisites
Before creating Multistep Checks, ensure you have:
- An initialized Checkly CLI project
- Public endpoints you want to monitor
- Runtime
2023.09or later (Multistep Checks require newer runtimes)
Configuration
- Multistep Check
- General Check
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
code | object | ✅ | - | The Playwright test code |
Multistep Check Options
The Playwright test code that defines your Multistep Check monitor.Usage:Parameters:
Examples:Use cases: Complex API journeys, end-to-end API workflows, business process validation.
| Parameter | Type | Required | Description |
|---|---|---|---|
entrypoint | string | ❌ | Path to a .spec.js or .spec.ts file containing the Playwright test |
content | string | ❌ | Inline JavaScript/TypeScript code as a string |
You must provide either
entrypoint or content, but not both.- CRUD API
- Degraded state
General Check Options
Friendly name for your multistep check that will be displayed in the Checkly dashboard and used in notifications.Usage:
The Checkly runtime version used to execute the Multistep Check. Runtimes are managed execution environments for Browser and Multistep Checks. They include fixed Checkly-provided dependencies, such as Playwright, browser binaries, and runtime libraries.Multistep checks require runtime
2023.09 or later.Usage:How often the multistep check should run. Use the Available frequencies:
Frequency enum to set the check interval.Usage:EVERY_1M, EVERY_2M, EVERY_5M, EVERY_10M, EVERY_15M, EVERY_30M, EVERY_1H, EVERY_2H, EVERY_3H, EVERY_6H, EVERY_12H, EVERY_24HArray of public location codes where the multistep check should run. Multiple locations provide geographic coverage and user experience insights.Usage:Examples:Use cases: Global API monitoring, regional API testing, geographic compliance validation.
- Global User Experience
- Regional Focus