Skip to content

Scheduling

Scheduling controls when a suite runs.

Schedule types

Four schedule types are available:

manual: run only when triggered from UI or API
interval: run every N minutes
on_every_n_blocks: run when a specified number of new blocks are detected
on_timestamp: run at a specific time or cron-like schedule

Interval scheduling

Use interval mode for predictable test cadence.

Example frequencies:

1 minute for high-sensitivity smoke checks
5 minutes for standard production checks
15+ minutes for heavier regression suites

Tradeoff:

lower interval catches issues faster
lower interval increases run count and resource usage

Block-based scheduling

on_every_n_blocks triggers after a configured number of new blocks on the chain.

Requirements:

observer active for the chain/endpoints
at least one healthy endpoint to detect progress

Best for:

rollups and chains where block cadence is signal-critical
detecting block-boundary regressions

Timestamp scheduling

on_timestamp triggers runs at a configured time. Useful for daily or weekly deep checks on a fixed cadence.

Manual mode

Manual mode is useful for:

template tuning
incident investigation
CI-triggered ad-hoc checks

Practical policy example

Production smoke suites: interval 5m
Cross-provider comparison suites: interval 10m
Upgrade deep checks: manual during maintenance window
Final post-upgrade monitor: on_every_n_blocks for first hour