Wolfix
Running Scans
Back to help center

Step-by-step · Running Scans

Scheduling recurring scans

Put your scans on autopilot so new gaps surface on their own.

Reviewed by OperationsUpdated May 28, 20262 min readSuggest edit

You'll need

A connected project with one completed scan

Time

~2 min to configure

Plan

Recurring scans vary by plan — see /pricing

A one-off scan is a snapshot. A schedule keeps it current. Once you set a cadence, Wolfix re-scans on its own and flags anything new — a legal page that drifted out of date, an expired DNS record, a tracker a deploy quietly added. This is the monitoring layer: it catches regressions before a customer does.

Open project settings

From your dashboard, open the project you want to monitor and go to its Settings tab. Recurring scans are configured per project, so each one keeps its own cadence.

Fig. 01 — Project settings: the recurring scans section · screenshot pending

Choose a cadence

In the Recurring scans section, pick how often Wolfix should re-scan: weekly or monthly are the common choices. Weekly suits a project that ships often; monthly is enough for a stable app where the surface rarely changes.

Set the cadence to the rhythm of your changes, not to the calendar — there is no benefit to scanning faster than you deploy.

Pick the scan mode

Choose whether each scheduled run is a quick scan or a deep scan. A deep scan gives you full coverage every cycle; a quick scan is lighter and faster if you mainly want to watch document- and code-level gaps. Most projects on a monitoring cadence use a deep scan so DNS and provider drift is caught too.

Fig. 02 — Recurring scan configuration: cadence and mode · screenshot pending

Save and confirm

Save the settings. Wolfix shows the next scheduled run date so you can confirm the cadence took effect. The first scheduled scan runs at the next interval — your most recent manual scan stays the active report until then.

Scheduled scans run on their own

You do not need to keep a tab open or be signed in. Scheduled scans run in the background and the results appear in your dashboard when they finish.

Review what changed

After a scheduled scan completes, open the new report. Each run is stored separately, so you can compare it against the previous one and see exactly which findings are new, which were resolved, and which still stand.

A schedule does not fix anything

Recurring scans surface gaps — they never resolve them. New findings still need you to generate the asset, apply the code fix, or follow the referral from the report.

You just did

Your project is now monitored

  • Opened the recurring scans section in project settings
  • Chose a cadence that matches how often you ship
  • Picked a scan mode for each scheduled run
  • Confirmed the next scheduled run date
  • Know where to review what changed between runs

Was this article helpful?