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

# Schedules

> How to view and edit the schedules that start Prizm jobs, run a scheduled job on demand, and review autonomous schedules in the Command Center.

## Overview

The **Schedule** page lists every schedule in your organization. A schedule decides when a job runs against a source or an asset. This page has two tabs: **Schedule**, for standard schedules, and **Autonomous**, for schedules Prizm generates from asset criticality.

For the default cadence of each job type, see [Scheduling](/architecture/scheduling).

## Navigating there

From the left-hand navigation:

```text theme={null}
Command Center → Schedule
```

## Schedule tab

The **Schedule** tab shows the total number of schedules in the title, for example `Schedule (405)`.

![Schedule tab listing each schedule with its name, description, level, active toggle, next run and type](https://mintcdn.com/dqlabs/-llXdpktU4fg82jU/images/command-center/schedule-tab.png?fit=max\&auto=format\&n=-llXdpktU4fg82jU\&q=85\&s=64b94ee44979207004b41f6a1746f832)

### Table columns

| Column | Description |
| - | - |
| **Name** | The job the schedule starts, for example `Asset Deletion Scan`, `Compute Metric`, `Structural Recommendation`, or `Operational` |
| **Description** | A readable summary of the cadence, for example `Every day at 2:30 AM (UTC)` or `Every 1440 hours (Asia/Kolkata)` |
| **Level** | Whether the schedule applies to a whole **SOURCE** or to a single **ASSET** |
| **Is Active** | A toggle that shows whether the schedule is on. Turn it off to stop the job from running on this schedule |
| **Next Run At** | The date and time of the next planned run |
| **Type** | How the schedule was created, for example `AUTO` |
| **Asset Name** | The asset the schedule applies to. Blank for source-level schedules. Not shown by default; add it with **Select Columns** |
| **Source Name** | The source the schedule belongs to. Not shown by default; add it with **Select Columns** |
| **Action** | Buttons to edit the schedule, run it now, and open related logs (see below) |

### Row actions

| Action | What it does |
| - | - |
| **Edit** | Opens the **Edit Schedule** panel |
| **Run job now** | Runs the job immediately without changing the schedule |
| **View Job Log** | Opens the job log for this schedule's jobs |
| **Audit Log** | Opens the audit log entries for this schedule |

![Schedule table scrolled right showing the Is Active toggle, Next Run At, Type and four action icons](https://mintcdn.com/dqlabs/-llXdpktU4fg82jU/images/command-center/schedule-row-actions.png?fit=max\&auto=format\&n=-llXdpktU4fg82jU\&q=85\&s=52638482408a492fe3e6210003f320a1)

The table toolbar has controls to filter, sort, and search the list, the same as on the [Job](/architecture/command-center/jobs) page. Filter fields include Name, Level, Is Active, Next Run At, Schedule ID, Source Name, Asset Name, and Metric Name. The **More** menu has **Select Columns**, **Download**, **Bulk Edit**, and **Reset Preference**.

### Edit a schedule

Select **Edit** on a row to open the **Edit Schedule** panel. Updating a schedule replaces the existing one and applies to all future runs.

![Edit Schedule panel with Start Date, Schedule Type, Repeat every, Schedule Name and Time Zone fields](https://mintcdn.com/dqlabs/-llXdpktU4fg82jU/images/command-center/schedule-edit-panel.png?fit=max\&auto=format\&n=-llXdpktU4fg82jU\&q=85\&s=ef4eb01a715edc1f3ce1958647b1b97d)

| Field | Description |
| - | - |
| **Start Date** | The date and time the schedule starts from |
| **Schedule Type** | **Calendar**, **Cron**, or **Event** |
| **Schedule Name** | A label for the schedule |
| **Time Zone** | The time zone used to calculate run times, for example `(UTC +00:00) UTC` |

The remaining fields depend on the schedule type.

**Calendar**

Use **Calendar** for a regular interval.

| Field | Description |
| - | - |
| **Repeat every** | A number and a unit, for example `3` `HOURS` or `1` `DAYS` |
| **Occurrence** | The time of day the job runs, for example `02:30`. Select **Add Time** to run it at more than one time of day |

The panel shows a **Next run** line that previews when the job will run next, so you can check the result before you save.

**Cron**

Use **Cron** when you need a cadence a fixed interval cannot express.

| Field | Description |
| - | - |
| **Cron expression** | A standard five-field expression in the order minute, hour, day, month, weekday, for example `0 0 * * *` |

The **Next run** line shows `Based on cron expression`.

**Event**

Use **Event** to trigger the job from an event instead of at a fixed time.

Select **Submit** to save the schedule, or **Cancel** to close the panel without changes.

> [!WARNING]
>
> Hourly is the practical minimum cadence. See the note in [Scheduling](/architecture/scheduling) about sub-hourly intervals.

## Autonomous tab

The **Autonomous** tab lists schedules that Prizm creates and manages for you, for example `Autonomous Schedule (357)`. Autonomous schedules follow the profiling cadence Prizm recommends for each asset, based on its criticality and scope.

| Column | Description |
| - | - |
| **Asset ID** | Unique identifier of the asset |
| **Asset Name** | The asset the schedule applies to |
| **Profile Type** | The profile depth, for example `ESSENTIAL` or `ADVANCED` |
| **Profile Scope** | How much of the asset is profiled, for example `FULL` |
| **Criticality** | The asset's criticality level: `LOW`, `MEDIUM`, `HIGH`, or `CRITICAL` |
| **Criticality Score** | The asset's score on a P0 to P100 scale, for example `P37` |

![Autonomous tab listing assets with their asset ID, name, profile type, profile scope and criticality](https://mintcdn.com/dqlabs/-llXdpktU4fg82jU/images/command-center/schedule-autonomous.png?fit=max\&auto=format\&n=-llXdpktU4fg82jU\&q=85\&s=b1eb9ef5daf895997c093952b8376870)

Profile Type and Profile Scope can be blank for an asset until Prizm has a profiling recommendation for it.

Use this tab to see which assets Prizm is scheduling for you and the criticality that drives each schedule.

## Common tasks

* **Pause a schedule** — turn off **Is Active** on its row.
* **Change how often a job runs** — select **Edit**, choose **Calendar** or **Cron**, and select **Submit**.
* **Run a job outside its schedule** — select **Run job now**. The schedule itself is not changed.
* **Check whether a schedule ran** — select **View Job Log**, or open the [Job](/architecture/command-center/jobs) page and filter by **Schedule Name**.

## Permissions

Viewing schedules needs **Command Center – Schedule** View. Changing a schedule needs Edit, and Approve lets a role approve a proposed change before it takes effect. See [Role-Based Access Control](/security/rbac).

## Related pages

> **[Jobs](/architecture/command-center/jobs)**
>
> See the runs a schedule started

> **[Scheduling](/architecture/scheduling)**
>
> Default schedules for each job

> **[Audit Log](/architecture/log/audit-log)**
>
> Review changes and runs in the audit trail

> **[Command Center Overview](/architecture/command-center/overview)**
>
> All Command Center sections


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