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

# Jobs

> The job list at /jobs: filters, bulk actions, sweep badges, and the submission ledger.

Every job you can see, newest first, at `/jobs`. Click a row for its
[detail view](https://docs.tuneplane.ai/en/console/job-detail.md).

![TunePlane jobs list](https://mintcdn.com/starforge/GatXR2rI5-_Vm4_H/images/console/jobs.png?fit=max\&auto=format\&n=GatXR2rI5-_Vm4_H\&q=85\&s=daa2d6bc21d7efdfce3d1690f9ca6bad)

Jobs list. Filter by status or project; click a row for details.

## What you see

| Column | What it is |
| - | - |
| **Status** | The ledger state, not the backend's. See [job states](https://docs.tuneplane.ai/en/concepts/job-lifecycle.md) |
| **Method** | `<framework>/<method>` from the run's lock file |
| **GPUs** | Cards held. This is what quota counts |
| **Duration** | Time since the container came up, not since submission |
| **Retries** | How many attempts this run has had, automatic ones included |
| **Sweep** | A badge when the job belongs to a sweep, so a grid reads as one group |

Filter by status, user or project. The search box matches project, user, run id and profile.

A job the list shows as one row may be a **Pipeline** of several Steps — one row, with a state
rolled up from them. `partial` there means training succeeded and something declared after it did
not happen.

## What you can do

| Action | Where it goes |
| - | - |
| Click a row | [Job detail](https://docs.tuneplane.ai/en/console/job-detail.md): charts, logs, validation, artifacts |
| Stop, pause, resume, delete | Inline on the row, or `tp job stop` and friends |
| Select several rows, then **Review** | [Compare them](https://docs.tuneplane.ai/en/console/review.md) |
| Copy a run id | For `--init-from`, `tp bench run -m run:<id>`, or a support thread |
| **Share** | A read-only public link. See [sharing](https://docs.tuneplane.ai/en/guides/sharing.md) |

Stopping is not a delete. A stopped job keeps its record, its metrics and its artifacts, and can
be retried under the same run id.

## The ledger view

`?view=ledger` switches the same page to the server's submission record: who submitted what,
when, on which profile, and what became of it.

| Column | What it is |
| - | - |
| **Run ID** | The identity everything else refers to: artifacts, `--init-from`, share links |
| **Project** | From `name` in `tuneplane.yaml`, attached at submission |
| **User** | Who submitted it |
| **Profile** | The hardware requested |
| **State** | Where it ended up |

It used to be its own page at `/runs`. Two sidebar entries over one set of records left people
guessing which to open, so it became a view. The old link still lands here.

## Runs and jobs are not the same thing

A **job** is the unit of scheduling. It can be paused, resumed and retried, and each attempt is
the same job.

A **run** is the unit of record. Its directory holds the working copy, the outputs and the
archived logs, and it is what storage accounting and reclamation operate on.

That distinction matters when you reference an earlier result:

```bash theme={"theme":{"light":"github-light","dark":"github-dark-dimmed"}}
tp submit my-dpo --profile h200:8 --init-from run/run-4f2a91/checkpoint@step=500
```

That is a run id, because what you want is the artifact, which outlives the job that produced it.

## Next

[Job detail](https://docs.tuneplane.ai/en/console/job-detail.md) · [Review](https://docs.tuneplane.ai/en/console/review.md) ·
[Projects](https://docs.tuneplane.ai/en/console/projects.md) · [Job states](https://docs.tuneplane.ai/en/concepts/job-lifecycle.md)


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