> ## 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.

# Scheduling

> CRON, event-based, and AI-driven intelligent schedule management.

<script type="application/ld+json">
  {`{
            "@context": "https://schema.org",
            "@type": "TechArticle",
            "headline": "Scheduling",
            "description": "CRON, event-based, and AI-driven intelligent schedule management.",
            "url": "https://docs.dqlabs.ai/architecture/scheduling",
            "publisher": {
              "@type": "Organization",
              "name": "DQLabs Inc",
              "logo": "https://media.brand.dev/332adc35-5bc4-4d2b-bf78-256aa4a5e414.svg"
            }
            }`}
</script>

## Overview

Every job Prizm runs against a connected source follows a schedule. Schedules for the core metadata-synchronization jobs are created automatically when a source is configured; custom metric schedules can be created manually. You can view and override any job's schedule from the connector detail page, or from an individual asset's **Overview** tab via the **Open schedule** link.

## Default schedules by job

| Job                                            | Default cadence                                                                          |
| ---------------------------------------------- | ---------------------------------------------------------------------------------------- |
| Technical (catalog)                            | Daily — first job in the pipeline                                                        |
| Operational (volume, freshness, schema change) | Hourly                                                                                   |
| Governance                                     | Runs in parallel after Operational completes                                             |
| Performance                                    | Daily                                                                                    |
| Usage Summary                                  | Runs in parallel after Operational completes                                             |
| Compute Metric                                 | Runs in parallel after Operational completes                                             |
| Lineage                                        | No schedule — runs only when triggered manually from an individual asset                 |
| Profile (Structural quality)                   | Runs on the schedule generated by Profile Recommendation, based on criticality and scope |

**How overrides work:** updating a schedule replaces the existing one and applies to all future executions. Triggering a job manually runs it immediately without disturbing its configured schedule.

<Warning>
  **Sub-hourly scheduling is not a documented, supported cadence today.** The only cadence Prizm documents for the Operational job is hourly. In testing, a job configured with a 5-minute interval was observed collecting roughly every 30 minutes rather than every 5 — there is no published minimum interval or enforced floor for sub-hourly values. Until a supported minimum is confirmed, treat **hourly as the practical floor** and don't rely on a sub-hourly interval reflecting the configured cadence exactly.
</Warning>

For related information, see the [Platform Overview](/platform/overview) and [Architecture Overview](/architecture/overview).