> For the complete documentation index, see [llms.txt](https://copilot-docs.bugbase.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://copilot-docs.bugbase.ai/enterprise/activity/scheduling.md).

# Scheduling

Schedules start configured runs later or on a recurring cadence. Create them from the same Run Assessment wizard used for immediate work so the schedule captures the selected targets, settings, agent assignment, and safety controls.

## Create a Schedule

From the applicable **Run Assessment** page:

1. Choose the intent when the assessment type supports it.
2. Select targets, repositories, or subnets.
3. Configure authentication, rates, exploit controls, exclusions, agents, and other run-specific options.
4. In **Automation**, enable scheduling.
5. Choose:
   * **Doesn't repeat** and a future run time; or
   * **Repeats** with an interval and unit.
6. Confirm the complete configuration in **Review**.
7. Select **Schedule run**.

The schedule modal supports interval units of minutes, hours, and days.

{% hint style="info" %}
Schedules are created from a configured run, not from an empty scheduler form.
{% endhint %}

## Manage Schedules

Open **Activity -> Schedule**.

Use this page to:

* switch between one-time and recurring schedules;
* filter by schedule status;
* open schedule details, including the saved payload and scan configuration reference;
* delete schedules.

The Activity schedule page is for reviewing and managing schedules. Start new schedules from the relevant module's run flow.

## Important Behavior

Schedules use the payload and saved scan configuration created when the schedule is submitted. If you later change browser sessions, rate limits, allowed exploits, trajectory scope, target scope, responder/PCE Intercept settings, exclusions, or agent assignment, review whether the schedule must be recreated.

Recurring schedules reuse the stored run payload each time they fire. Confirm that the selected agents, credentials, browser sessions, and target scope will still be valid for each future run window.

## Before Scheduling Production Scans

Confirm:

* the scan window is approved;
* the required agents are expected to be online;
* browser sessions will still be valid;
* rate limits match the target's production capacity;
* internal exploit families are approved for the scheduled window;
* reports and on-call contacts are planned for high-impact runs.