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

# Jobs

> How to monitor every job Prizm runs across your organization, filter by status, source, or asset, run a job on demand, and open its log.

## Overview

The **Job** page lists every job Prizm has run in your organization, such as catalog sync, performance, and profiling jobs. Use it to confirm that scheduled work completed, find jobs that failed, and run a job again on demand.

## Navigating there

From the left-hand navigation:

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

The page title shows the number of jobs that match the current filters, for example `Job (3.046K)`.

![Job page with the ALL, PENDING, RUNNING, COMPLETED, FAILED and KILLED status filters above the job table](https://mintcdn.com/dqlabs/-llXdpktU4fg82jU/images/command-center/jobs-table.png?fit=max\&auto=format\&n=-llXdpktU4fg82jU\&q=85\&s=08569a8c2b147fcd5ce9af8cf6638fa7)

## Status filters

A row of buttons above the table narrows the list by job status. Each button shows how many jobs have that status.

| Filter | Shows |
| - | - |
| **ALL** | Every job, regardless of status |
| **PENDING** | Jobs that are queued and have not started |
| **RUNNING** | Jobs that are executing now |
| **COMPLETED** | Jobs that finished successfully |
| **FAILED** | Jobs that ended with an error |
| **KILLED** | Jobs that were stopped before they finished |

## Table columns

| Column | Description |
| - | - |
| **Job ID** | Unique identifier of the job run |
| **Name** | The kind of job, for example `OPERATIONAL`, `REPORT`, or `PIPELINE`. See [Scheduling](/architecture/scheduling) for what each job does |
| **Source Name** | The connected source the job ran against |
| **Status** | Current status of the job (see the filters above) |
| **Start Time** | When the job started |
| **End Time** | When the job finished |
| **Duration** | How long the job ran, for example `1m 11s 180ms` |
| **Action** | Buttons to run the job again or open its log (see below) |

The table is wider than most screens, so scroll to the right to reach **Status**, **Duration**, and **Action**.

![Job table scrolled right showing the Status, Start Time, End Time, Duration and Action columns](https://mintcdn.com/dqlabs/-llXdpktU4fg82jU/images/command-center/jobs-table-right.png?fit=max\&auto=format\&n=-llXdpktU4fg82jU\&q=85\&s=02ae84ddc044c7ad7a64f5f8e10283f9)

## Filtering, sorting, and searching

The toolbar at the top right of the table has four controls: filter, sort, search, and **More** (the three dots). Select the filter icon and choose a field from the **Filter by…** list. You can filter on any of these fields:

* Asset ID and Asset Name
* Created At, Start Time, End Time, and Duration
* Error Message
* Job ID and Name
* Metric Detail ID and Metric Name
* Schedule ID and Schedule Name
* Source ID
* Status

The **More** menu has **Select Columns**, **Download**, and **Reset Preference**.

> [!TIP]
>
> To find out why a job failed, select the **FAILED** filter and add a filter on **Error Message**. Then open the job's log with the action buttons described below.

## Row actions

Each row has two action buttons, the play icon and the job icon:

| Action | What it does |
| - | - |
| **Run job now** | Runs the job immediately. This does not change the job's configured schedule |
| **Job Log** | Opens **Command Center → Log → Audit**, filtered to this job's ID, so you can see the events it recorded |

## Common tasks

* **Confirm a schedule ran** — filter by **Schedule Name** or **Source ID**, then check the **Start Time** and **Status** of the latest rows.
* **Investigate a failure** — select **FAILED**, open the **Job Log**, and review the entries in the [Audit Log](/architecture/log/audit-log).
* **Re-run a job** — select **Run job now** on the row.

## Related pages

> **[Schedules](/architecture/command-center/schedule)**
>
> Change when jobs run

> **[Audit Log](/architecture/log/audit-log)**
>
> Review the events a job recorded

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

> **[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.