The Scheduler feature allows you to automate workflow execution by scheduling them to run at specific dates and times, or on recurring intervals. This eliminates the need for manual execution and ensures your tests run consistently without human intervention.
Why Use Scheduling?
Run tests automatically without manual intervention—schedule them for off-hours to not interfere with development.
Ensure tests run at consistent times and frequencies with zero human error.
Schedule resource-intensive tests during low-usage periods to maximize system resources.
Implement continuous regression testing by scheduling nightly or weekly test runs.
Creating a Schedule
Basic Schedule Setup
Open your workflow in Test Orchestration
Click "Schedule" or find scheduling options
Choose schedule type: One-time or Recurring
Set execution time and frequency
Configure notifications (optional)
Save schedule
One-Time Schedule
Use for:
Running tests at a specific date/time
Post-deployment testing
Emergency regression runs
Scheduled maintenance tests
Steps:
Select "One-Time" schedule type
Choose date and time
Set timezone
Add description (optional)
Click "Schedule"
Recurring Schedule
Use for:
Nightly test runs
Weekly regression suites
Daily smoke tests
Monthly performance tests
Recurrence Options:
Daily
Weekly (choose specific days)
Monthly (choose specific dates)
Custom (create advanced patterns)
Schedule Configuration
Time Settings
Schedule Frequency Examples
Daily at 2:00 AM
Every Monday at 9:00 AM
First and Third Friday of each month
Managing Schedules
View All Schedules
Go to Workflow Dashboard
Click "Scheduled Runs" tab
View all scheduled workflows and their next execution time
Edit a Schedule
Find the scheduled workflow
Click "Edit Schedule"
Modify time/frequency/settings
Save changes
Disable/Pause a Schedule
Find the scheduled workflow
Click "Pause Schedule" or toggle off
Schedule will be paused (not deleted)
Re-enable anytime by clicking "Resume"
Delete a Schedule
⚠️ Important: Deleting a schedule will stop future executions. The workflow itself is not deleted, only the schedule.
Find the scheduled workflow
Click menu (three dots)
Select "Delete Schedule"
Confirm deletion
Notifications & Alerts
📧 Stay Informed
Get automatic notifications when your scheduled workflows execute. Know immediately if something fails.
Schedule Execution Notifications
Configure who gets notified when scheduled workflows run:
Open workflow
Click "Schedule Settings"
Configure notifications:
Run started
Run completed
Run failed
Run with warnings
Notification Recipients
📧 Email addresses (comma-separated)
💬 Slack channels
👥 Microsoft Teams channels
🔗 Webhooks
🔌 Custom integrations
Notification Content
Notifications include:
✅ Workflow name and status
⏱️ Execution time and duration
📊 Pass/fail summary
📋 Link to detailed reports
Best Practices
What to Do
✅ Stagger schedules - Avoid running many workflows simultaneously
✅ Use off-peak hours - Schedule during low-activity periods
✅ Set timezone explicitly - Prevent confusion across regions
✅ Monitor initial runs - Watch first few scheduled runs to ensure they work
✅ Document the purpose - Add descriptions to scheduled workflows
✅ Review regularly - Check which workflows are scheduled quarterly
✅ Set expiration dates - End obsolete schedules
✅ Test before scheduling - Run workflow manually first
What to Avoid
❌ Don't schedule all tests simultaneously - Causes resource contention
❌ Don't forget about schedules - Orphaned schedules waste resources
❌ Don't ignore failed notifications - Monitor schedule execution status
❌ Don't use system peak hours - Interferes with production usage
❌ Don't neglect timezone settings - Causes scheduled runs at wrong times
❌ Don't over-schedule - Too many concurrent runs reduce performance
One-Time Execution
├── Date: Select date picker
├── Time: Enter specific time
├── Timezone: Choose your timezone
└── Description: Document the schedule
Recurring Execution
├── Frequency: Daily/Weekly/Monthly/Custom
├── Start Date: When to begin
├── End Date: When to stop (optional)
├── Time of Day: When each run occurs
├── Days/Dates: Specific occurrences
└── Timezone: Choose your timezone
Frequency: Daily
Time: 02:00 AM
Timezone: UTC
Frequency: Weekly
Days: Monday
Time: 09:00 AM
Timezone: UTC
Step 1: Data setup (1 AM)
Step 2: Main tests (2 AM) - Depends on setup
Step 3: Cleanup (3 AM) - Final validation
Workflow: Complete-Regression-Suite
Schedule: Daily at 2:00 AM UTC
Frequency: Every day
Notifications: QA Team email, Slack #testing
Description: "Comprehensive regression test suite"
Workflow: Smoke-Test-All-Platforms
Schedule: Every Monday at 9:00 AM UTC
Also runs: Every Thursday at 3:00 PM UTC
Frequency: Weekly on Mon & Thu
Notifications: Team leads via email
Description: "Quick smoke tests for all platforms"
Workflow: Post-Deploy-Validation
Schedule: Manual + One-time
Triggered: After production deployment
Notifications: DevOps team + QA lead
Description: "Critical tests after production release"
Workflow: Performance-Regression
Schedule: First Monday of each month at 1:00 AM
Frequency: Monthly
Notifications: Performance team email
Description: "Monitor performance metrics over time"
Workflow A runs at 2:00 AM
↓
Workflow B runs after A completes successfully
↓
Workflow C runs only if B failed (remediation)
0 2 * * * = Daily at 2:00 AM
0 9 * * 1 = Every Monday at 9:00 AM
0 1 1 * * = First day of month at 1:00 AM
0 */6 * * * = Every 6 hours
