A single scan tells you what is true right now. A schedule tells you what changed, which is almost always the more useful thing.
Set one up for a scan, capture, survey, or permutation check, or all of them. The schedule keeps running on its own. Each run is recorded, so you can compare this week to last week instead of trying to remember.
This is how monitoring actually happens
Most of the reasons to use Efflux turn into a schedule eventually. Watching that a service stays reachable, noticing a port that opened after a deploy, catching a lookalike domain while it is being set up: none of that works as a one-off. It works because something ran again and the answer was different.
Pick a cadence that matches the question
Scans can run as often as hourly, which suits availability and perimeter checks. Captures and permutation checks start at daily. Surveys start at weekly, which is usually right, since a subdomain inventory does not change by the hour.
Slower is often better. A daily check you actually read beats an hourly one you learn to ignore.
It keeps up with your configuration
A schedule stores the targets you configured, and it re-checks your callback settings on every run. Empty callback phases get filled from your preferences when the job runs, not when you saved the schedule, so updating a destination once applies to everything that follows.
Where to go next
Schedules covers the timing fields, the fastest frequency for each target, and how to pause one.