Skip to main content

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

​
Where to see schedules

Every schedule in your organization is listed under Command Center → Schedule. Open Command Center from the document icon on a row in the Source list. The Schedule tab shows each schedule’s name, description (for example Every 1 hour (UTC)), level (Source or Asset), an Is Active toggle, the next run time, and its type (Auto for schedules Prizm created).
Command Center Schedule tab listing schedules with description, level, active toggle and next run

Command Center → Schedule: every schedule with its cadence and next run

The Autonomous tab lists the assets whose profiling schedule Prizm chooses for you, with each asset’s profile type, profile scope, criticality, and criticality score.
Autonomous schedule table with asset name, criticality and criticality score

Command Center → Schedule → Autonomous

​
Default schedules by job

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.
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.
For related information, see the Platform Overview and Architecture Overview.