Blackout Periods
Blackout periods prevent an audit or Journey from starting during that time frame. These periods are useful for preventing scans of the site when you know the site will return bad data, such as when the site is undergoing maintenance or updates.
Note: Blackout periods do not pause a run that is already in progress. It only prevents a run from being initiated.
Runs that would start during the blackout are skipped. If an audit is set to run daily during the blackout, the audit will never run because the highest frequency for an audit is daily. The exception to this is if the audits are backed up and the start time is delayed due to too many audits in the queue. In that case, if the audit start time is pushed until after the blackout, it will run.
The following scenarios illustrate the rules.
Scenario #1: Journey Set to 15 Minutes
Type: Journey
Frequency: 15 minutes
Start Time: 1:00 AM
Blackout Period: 2 AM - 3 AM
| Start Time | Result |
|---|---|
| 1:00 AM | Run |
| 1:15 AM | Run |
| 1:30 AM | Run |
| 1:45 AM | Run |
| 2:00 AM | Skipped |
| 2:15 AM | Skipped |
| 2:30 AM | Skipped |
| 2:45 AM | Skipped |
| 3:00 AM | Skipped |
| 3:15 AM | Run |
Scenario #2: 1,000 Page Audit Set to Once a Day
Type: Audit
Frequency: Daily
Start Time: 1:00 AM
Blackout Period: 1:15 AM - 4:15 AM
| Start Time | Result |
|---|---|
| 1:00 AM | Run |
Scenario #3: 1,000 Page Audit Set to Once a Day
Type: Audit
Frequency: Daily
Start Time: 3:00 AM
Blackout Period: 2:00 AM - 4:00 AM
| Start Time | Result |
|---|---|
| 3:00 AM | Skipped |