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

# Runs

> The submission ledger: every job the server admitted, newest first.

A server-side ledger of submissions — who submitted what, when, on which profile, and what became of
it. Each `run_id` links through to the job.

<Frame caption="Submission ledger: every admitted job, newest first.">
  <img src="https://mintcdn.com/starforge/GatXR2rI5-_Vm4_H/images/console/runs.png?fit=max&auto=format&n=GatXR2rI5-_Vm4_H&q=85&s=497d32a7f417e9a51dec089f52f0bbda" alt="StarForge submission ledger" width="2160" height="1350" data-path="images/console/runs.png" />
</Frame>

## What you see

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

Search matches across project, user, run id and profile.

## Runs and jobs are not the same thing

A **job** is the unit of scheduling — it can be paused, resumed, 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.

This matters when you reference a previous result:

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

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

## What you can do

* Click a run to open its [job detail](/en/console/job-detail).
* Search or filter, then copy a run id for `--init-from` or `sf bench`.
* Follow a run into [Projects](/en/console/projects) to see it in the context of its repository.