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.

Who should read this

  • QA engineers, SREs, platform teams, and developers operating Zof Console and APIs.

When to use this workflow

  • Onboarding new team members to Zof terminology and workflows
  • Authoring internal runbooks aligned with Console labels
  • Designing CI/CD or webhook integrations against documented behavior

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.

Best practices

  • Validate changes in staging before applying release gates to production.
  • Include run IDs and timestamps when escalating issues to support or auditors.
  • Align internal runbook terminology with Zof Console UI labels for clarity.

Was this page helpful?

Scheduling | Zof AI Documentation