S4E Cloud continuously runs automated scans against your assets. In Manage > Manager > Schedule you do not define when scans start; instead you configure skip windows — days and hours when scans must not run (for example during maintenance or peak traffic).


Why Use Skip Windows?

Skip rules help you:

  • Avoid disruption -- Hold scans during maintenance, releases, or sensitive business hours.
  • Protect performance -- Reduce load on production systems when traffic is highest.
  • Stay in control -- Apply rules to one asset or to every verified asset using a single configuration.

Beta

Skip process is live in beta. After you create or change a rule, verify behaviour in the UI or contact S4E if something looks incorrect.


Opening the Skip Configuration Modal

  1. Navigate to Manage > Manager > Schedule.
  2. Click Configure where you manage skip behaviour, then choose Skip (modal title: Add Skip Configuration).

The modal shows the Beta notice at the top: Skip process is live in beta. Please check manually after defining it or contact us.


Add Skip Configuration

Scope: which assets

  • Include all assets -- When enabled, the skip rule applies organisation-wide (all verified assets). When disabled, choose one asset in Select your verified asset.
  • Select your verified asset -- Dropdown to pick a specific verified asset when Include all assets is off.

How long the rule lasts

  • Until Date (optional) -- Latest date when this exclusion stays valid. Help text in the UI: Please enter the maximum date for which this exclusion will be valid.

When scans are skipped (cron)

The skip window is defined with a cron expression:

  1. Ask AI to help you write a cron expression -- Describe the skip pattern in plain language (for example weekends only, or weekday nights). The UI notes that The date expression you entered will be converted to a cron expression by AI.
  2. Click Generate Cron Expression to fill the cron field when AI output is ready.
  3. Cron Expression -- The final cron string. You can also type or paste it manually.

UTC only

Cron expressions use UTC, not your local time zone. Convert your intended local windows to UTC before relying on manually written crons.

  1. Readable Cron Expression -- Human-readable summary of the cron string so you can double-check before saving.

  2. Click + Add to save the skip configuration (enabled when required fields are valid).


After You Save

The Schedule area lists configured skip rules. Typical columns include:

  • Asset -- The asset the rule applies to (or "All Assets" if organisation-wide).
  • Cron Expression -- The cron string defining the skip window.
  • Configuration -- Rule type (e.g. Skip).
  • Valid Until Date -- When the optional end date expires.
  • Actions -- Edit or delete the rule.

Examples

Goal Cron idea (always verify in UTC)
Weekend maintenance Skip during Saturday/Sunday UTC windows you choose.
Weekday business hours Skip Mondays--Fridays within your peak-hours range in UTC.
Deployment freeze Narrow window around release time, optionally combined with Until Date.

Adjust natural-language prompts for the AI helper until Readable Cron Expression matches what you expect.


What's Next?

  • Creating Scans -- Start scans from the guided flow when you need a manual run outside skip windows.
  • Scan Types -- Choose Single, Full, Light, or Crawl Only scans.