Console

Scheduling

Recurring validation schedules.

Overview

Schedules run recurring validation using cron expressions: nightly regression, pre-release smoke, hourly API health checks, and weekly security scans. Schedules respect agent capacity and environment tags.

Failed scheduled runs appear in Operate → Runs with schedule source label for alerting workflows.

Step-by-step procedure

Create schedule

Operate → Schedules → Create.

Define cron (e.g., 0 2 * * * for 02:00 UTC daily).

Select target suite or case set and environment.

Configure alerts

Link webhook or integration for consecutive failure notification.

Assign on-call reviewer in team settings.

Monitor

Confirm scheduled runs appear in Runs list with schedule badge.

Pause schedule during maintenance windows without deleting configuration.

Key concepts

Cron expression: Standard five-field schedule: minute hour day month weekday.
Paused schedule: Configuration retained; no triggers until resumed.

Account for overlap, timezones, and stale evidence

Record the intended timezone, target environment, selected scope, expected duration, and owner of each scheduled workflow. Review daylight-saving changes and maintenance windows when timing affects a business process.

Decide how your supported scheduler handles overlapping work and missed starts. Monitor whether a delayed result still applies to the relevant source revision or release. Reconcile schedules with CI triggers to avoid duplicate expensive runs.

Was this page helpful?