Skip to main content
Learn more about Multistep Checks in the Multistep Checks overview.
Use Multistep Checks to run complex end-to-end workflows with Playwright that span multiple endpoints. The examples below show how to configure Multistep Checks for different testing scenarios.
Before creating Multistep Checks, ensure you have:
  • An initialized Checkly CLI project
  • Public endpoints you want to monitor
  • Runtime 2023.09 or later (Multistep Checks require newer runtimes)
For additional setup information, see CLI overview.

Configuration

ParameterTypeRequiredDefaultDescription
codeobject-The Playwright test code

Multistep Check Options

code
object
required
The Playwright test code that defines your Multistep Check monitor.Usage:
Parameters:
ParameterTypeRequiredDescription
entrypointstringPath to a .spec.js or .spec.ts file containing the Playwright test
contentstringInline JavaScript/TypeScript code as a string
You must provide either entrypoint or content, but not both.
Examples:
Use cases: Complex API journeys, end-to-end API workflows, business process validation.

General Check Options

name
string
required
Friendly name for your multistep check that will be displayed in the Checkly dashboard and used in notifications.Usage:
runtimeId
string
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:
Multistep checks require runtime 2023.09 or later. Earlier runtimes do not support multistep functionality.
frequency
Frequency
How often the multistep check should run. Use the Frequency enum to set the check interval.Usage:
Available frequencies: EVERY_1M, EVERY_2M, EVERY_5M, EVERY_10M, EVERY_15M, EVERY_30M, EVERY_1H, EVERY_2H, EVERY_3H, EVERY_6H, EVERY_12H, EVERY_24H
locations
string[]
default:"[]"
Array 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.
Multistep checks are only supported on runtime 2023.09 or later. Make sure to specify a compatible runtimeId in your check configuration.