01
1. Create the schedule
- Open /runs/schedules, use a name that identifies the target and purpose, and enter a public HTTP or HTTPS asset URL.
- Choose an interval from 1 to 168 hours. The current page creates `every_hours` schedules; daily and weekly cadence types exist in the API contract but are not offered by this form.
- The form creates a fixed staging template with quick scan, low attack depth, and the OWASP tag. Review that scope before relying on the schedule.
02
2. Check what was scheduled
- After creation, confirm that the list shows the target, scan profile, attack depth, cadence, and next run time you expected.
- Use Pause or Resume to control future triggers and Delete to remove the schedule. The page does not display `last_triggered_at` or a schedule-specific run history.
- Check the general runs list after the expected time and allow for scheduler or worker delay. A queued or completed run is evidence to inspect, not an automatic security conclusion.