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

# Configure and trigger scans in Detail

> Understand Detail's scan types and schedule, trigger on-demand scans from the dashboard, and inspect past scan runs with the CLI or dashboard.

Detail runs scans on a nightly schedule by default, so your bug findings stay fresh without any manual effort. You can also trigger on-demand scans at any time from the dashboard and configure exactly what each scan covers — whether that's a full repository scan or a focused look at recent changes.

## Scan types

<CardGroup cols={2}>
  <Card title="Full Repo" icon="magnifying-glass">
    A full repository scan against the latest commit on your primary branch. This is the standard scan type used for nightly runs.
  </Card>

  <Card title="Recent Changes" icon="code-branch">
    Scans only code introduced since a specific date or by specific authors. Faster than a full scan and useful for reviewing work in progress before merging.
  </Card>
</CardGroup>

## Scan schedule

Recurring scans run automatically — no configuration required. Detail picks up the latest commit on your primary branch each week and runs a Recent Changes scan. Detail also runs a Full Repo scan every month. Results appear in the dashboard as soon as the scan completes.

## Triggering an on-demand scan

You can kick off a scan at any time without waiting for the recurring schedule.

**From the dashboard:**

1. Go to **Scans** and find the repository you want to scan.
2. Click **Schedule New Scan** and follow the flow to select a repo.
3. The scan starts immediately. You'll see it appear under the **Scans** tab with an `in-progress` status.

## Inspecting scan history

**From the dashboard:** Click on a repository, then open the **Scans** tab. You'll see a list of past scan runs with their status, scan type, commit SHA, and bug counts.

**From the CLI:** Use `detail scans list` to view scan history for a repository.

```bash theme={null}
# List all scans for a repository
detail scans list owner/my-repo

# Filter by status and time range
detail scans list --status complete --since 7d
```

## Scan statuses

| Status        | Meaning                                                                              |
| ------------- | ------------------------------------------------------------------------------------ |
| `in_progress` | The scan is currently running. Results are not yet available.                        |
| `complete`    | The scan finished successfully. Bug findings are available in the dashboard and API. |
| `failed`      | The scan encountered an error and did not produce results.                           |

<Note>
  If a scan consistently shows a `failed` status, contact [support@detail.dev](mailto:support@detail.dev) with the repository name.
</Note>