Skip to content

Scheduling

Scheduling controls when scan traffic is allowed to run against your target. PhantomOps does not run on a calendar schedule (no “scan every Monday at 9am” — yet); instead, you give a project a working-hours window, and scans only fire inside it.

A project’s working-hours window is one of:

  • anytime — no time restriction; scans run whenever you launch them.
  • DAYS HH:MM-HH:MM TIMEZONE — e.g., Mon,Tue,Wed,Thu,Fri 09:00-17:00 Pacific/Auckland.

You set the window when you create or edit a project. See Create a project → Working hours for the field-level guidance.

Working hours block with timezone, day chips, and start/end time selectors

  • Hours snap to whole hours (00:00 through 23:00).
  • The end time must be after the start time. Overnight windows (e.g., 22:00–06:00) are not supported. To scan overnight, use Scan anytime.
  • Day presets: Mon–Fri, Mon–Sat, 7 days.
  • Supported timezones include Auckland, Sydney, Perth, Singapore, Tokyo, Mumbai, Dubai, London, Paris, US Eastern/Central/Mountain/Pacific, and UTC.

When you select Start scan:

  • If the current time is inside the window, the scan starts immediately.
  • If the current time is outside the window, the scan moves to the Scheduled state and starts automatically when the window next opens.

A scan in Scheduled waits in the queue. You can cancel it from the project’s Scans tab; it does not consume the assigned plan slot until the first agent actually starts.

If a scan is running when the working-hours window closes — for example, the run is ongoing at 17:00 and your window ends at 17:00 — PhantomOps pauses outgoing traffic to the target until the next window opens. Agents resume on schedule the next day.

You can stop a scan at any time from the Active Scan card in the sidebar; see Watch the scan.

  • On Starter, custom working-hours scheduling is unavailable. Starter projects run with anytime.
  • On Growth and Teams, the working-hours window is fully editable.

For the full plan-feature matrix, see Plans.