> ## Documentation Index
> Fetch the complete documentation index at: https://docs.perquery.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Scans and schedule

> Learn when Perquery scans a site, how to set the schedule and how to read the status of a scan.

A scan asks the AI engines of a site your prompts. Perquery asks each prompt for each persona and each AI engine that the site tracks. Then it reads your brand and your competitors out of the answers. The results show on the [Performance Overview](https://docs.perquery.ai/en/monitor/dashboard.md) and on the other monitor pages.

## When a scan runs

| Event | What Perquery scans |
| - | - |
| You finish the site setup | The first scan. It asks every prompt for each persona and AI engine. |
| The schedule of the site fires | A scheduled scan. |
| You add a prompt after the setup | A scan of the new prompt only, for each persona and AI engine. |

You cannot start a full scan by hand. After the first scan, full scans run only on the schedule.

Perquery does not scan an archived site. Perquery does not start a scan while the previous scan of the site still runs.

## Set the schedule

A new site scans once a week, on Monday at 6:00 AM, UTC. To change the schedule, do these steps:

**1. Open the site settings**

Open **Websites** and click **Configure** on the card of the site.

**2. Open the Schedule tab**

Click **Schedule**.

**3. Select the frequency**

In **Schedule**, select an option, for example **Every day at 9:00 AM**.

**4. Select the time zone**

In **Timezone**, select the time zone of the schedule.

**5. Save**

Click **Save**.

## How your plan changes a scan

Your plan sets how often a site can scan. You cannot select a schedule that scans more often than your plan allows.

On some plans, a scan does not ask every prompt. The **Schedule** tab then shows notes like these:

* How often your plan asks each prompt.
* How often your plan asks each persona.
* How a daily schedule shares the prompts across the days.
* The shortest time between two scans.

A daily schedule asks a share of the prompts each day. A less frequent schedule asks the prompts of every day since the last scan. For the plans, see [perquery.ai/en/pricing](https://perquery.ai/en/pricing).

## Read the status of a scan

The **Visibility scan** card on the **Performance Overview** shows the last scan of the site.

| Status | Meaning |
| - | - |
| **Running** | Perquery collects the answers. |
| **Finalising** | All answers are in. Perquery calculates the results. |
| **Completed** | The scan is complete. |
| **Partly completed** | The scan is complete, but some answers failed. |
| **Failed** | The scan collected no answer. |
| **Cancelled** | A user cancelled the scan. |

The card also shows these items:

* The progress bar and the number of collected answers.
* The counts: **Answered**, **Failed**, **Skipped** and **Outstanding**.
* The reasons of the failed answers, with a count for each reason, for example **Timed out**.
* The time when the scan started and the time when it finished.

If no scan ran yet, the card shows **No scan has run for this site yet. Scans run on a schedule.**

## Cancel a scan

To stop a scan that runs, click **Cancel** on the **Visibility scan** card. Perquery skips the answers that are not complete. The answers that Perquery collected before the cancellation stay.

## When a scheduled scan does not start

If a scheduled scan cannot start, Perquery sends an email to the owners of the organization. The email gives the reason, for example:

* The plan has no scans left for this period.
* The organization has no active subscription.
* The site has no prompts.
* The site has no personas.

Perquery tries again at the next scheduled time. It sends the email at most once a day for the same reason. To fix the cause, see [Billing and plans](https://docs.perquery.ai/en/account/billing-and-plans.md) or [Prompts](https://docs.perquery.ai/en/monitor/prompts.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.