Scheduled runs

Pro feature

Schedules require a Pro plan or above. Free workspaces see a locked Schedules item in the sidebar.

Automate test executions on a recurring daily or weekly cadence.

▶

Video coming soonCreating a scheduled run

Set up a daily or weekly regression schedule.

Concepts

Term	Meaning
Schedule	A recurring automation that runs tests at a set time
Hourly slot	One exclusive 1-hour window (UTC) per workspace: only one active schedule per slot
Batch Suite	A tag that groups snapshots: runs all members when the schedule fires
Snapshot list	Up to 5 individual snapshots, each run against its own org
Frequency	daily (every day) or weekly (one specific weekday)

Time is UTC

Schedules execute in UTC. The hour you pick (e.g. 09:00) is the UTC hour. Plan accordingly if your team works in a different timezone.

Create a schedule

1. Go to Schedules in the sidebar (/schedules).
2. Click Create Schedule.
3. Step 1: Target: choose Batch Suite (a tag) or Individual Snapshots (up to 5).
4. Step 2: Time & frequency: name the schedule, pick daily or weekly, and choose a free hourly slot.
5. Save.

Screenshot coming soonschedules-formCreate schedule form with target and frequency options

Choose what to run and when: batch suite or up to five snapshots.

Screenshot coming soonschedules-slot-pickerHourly slot picker showing available UTC time slots

Each workspace can have one active schedule per hourly slot.

Managing schedules

Action	Who
View schedules	Any workspace member
Create a schedule	Any workspace member
Edit or delete	Schedule owner or Workspace Admin
Pause / resume	Toggle is_active to pause without losing the slot

Slot conflicts

Only one active schedule can occupy a given hourly slot per workspace. If your preferred slot is taken, choose another hour or pause the conflicting schedule.

What happens when a schedule runs

1. At the scheduled UTC hour, Revsnap triggers the configured target.
2. For a batch suite, all snapshots in the tag run (up to three in parallel).
3. For individual snapshots, each snapshot runs against its connected org.
4. Results appear in Test Runs like any manual run.

Troubleshooting

Issue	Fix
Schedule did not run	Check that the schedule is active and the target tag/snapshots still exist
Slot unavailable	Another active schedule uses that hour: pick a different slot
Runs fail	Check org health: see Environment troubleshooting