Documentation
Learn how to configure capture schedules, timezones, trigger windows, and cloud storage — from first setup to production workflows.
Browse sections
Need help?
Contact SupportScheduling
Scheduling defines how often a Shot Schedule runs and when it is allowed to execute. Schedules run in your selected timezone, and you can further restrict execution using Trigger Windows.
A Shot Schedule always targets one URL. Scheduling decides the rhythm of capture jobs for that URL. Once saved, captures run automatically and are delivered to your connected cloud storage.
Where scheduling is configured
Scheduling is configured on the Shot Schedule. In the UI, you typically choose a Pre-Defined Capture Frequency, and then set the execution timezone.
Common fields used for scheduling
- • Pre-Defined Capture Frequency
- • Timezone (schedule runs in this local time)
- • Start Immediately or Start Date
- • End Date (optional)
- • Trigger Window (optional execution guard)
Pre-defined frequencies
Pre-defined frequencies are the simplest way to run captures on a fixed interval.
Hourly
Runs once per hour, every hour (timezone-aware).
Daily
Runs once per day at the configured capture time.
Weekly
Runs on selected weekday(s) at the configured time.
Monthly
Runs on selected day-of-month (or pattern) at the configured time.
Start and stop behavior
Scheduling supports both immediate execution and time-bounded capture windows.
- • Start Immediately — begin running as soon as the schedule is saved
- • Start Date — begin running at a specific date/time
- • End Date (optional) — stop running after a specific date/time
Example
Schedule a campaign landing page to run hourly starting Monday morning, then automatically stop after the campaign ends on Friday night using End Date.
Restrict execution with Trigger Windows
A schedule can be “due” to run, but still be blocked by a Trigger Window. This allows you to keep a frequency (like hourly) while limiting execution to specific days and hours.
Hourly interval example (business hours)
If a schedule is set to Hourly and you attach a Trigger Window like Mon–Fri, 09:00–17:00, the system will run captures only during those hours. Outside the window, runs are skipped until the next allowed time.
Timezone-aware scheduling
All scheduling is evaluated in your selected timezone. This keeps execution consistent through daylight saving changes and ensures “9 AM” really means 9 AM for the region you selected.
Why this matters
- • Campaign monitoring aligned to local business hours
- • Compliance evidence captured at exact regional times
- • Consistent “daily at 9 AM” behavior across DST shifts