How-to Guide
Schedule recurring test runs
Configure cron schedules for continuous validation.
Objective
Configure cron schedules for continuous validation.
Prerequisites
- Cases or suite ready
- Schedule permission
Procedure
Open Schedules
Operate → Schedules.
Navigation: Operate → Runs, Reports, or Schedules. Filter by project in large tenants to reduce noise.
Verification: Confirm organization and team context in the Console header before making changes.
Create schedule
Define cron expression and target cases.
Navigation: Operate → Runs, Reports, or Schedules. Filter by project in large tenants to reduce noise.
Verification: Note project, run, or agent IDs if you may need support escalation.
Enable and monitor
Confirm scheduled runs appear in Runs list.
Navigation: Operate → Runs, Reports, or Schedules. Filter by project in large tenants to reduce noise.
Verification: Confirm UI state matches your runbook. Retry once on transient errors before opening a ticket.
Verification checklist
- Confirm expected UI state or API response after each critical step
- Document run ID, project ID, or agent ID for support escalation if needed
- Notify stakeholders if the workflow affects release gates or production validation
Expected result
Recurring validation executes on schedule.
Was this page helpful?