> ## Documentation Index
> Fetch the complete documentation index at: https://wb-21fd5541-style-guide-models-runs-20260604-113608.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Run states

> Learn about the different states a W&B run can have.

The run state indicates the current status of a W\&B run. Check a run's state to confirm whether training is still in progress, has completed successfully, or has stopped unexpectedly. You can view the state of a run in the W\&B App or programmatically using the W\&B Python SDK.

## Run states

The following table describes the possible states a run can be in:

| State      | Description                                                                                          |
| ---------- | ---------------------------------------------------------------------------------------------------- |
| `Crashed`  | The run stopped sending heartbeats in the internal process, which can happen if the machine crashes. |
| `Failed`   | The run ended with a non-zero exit status.                                                           |
| `Finished` | The run ended and fully synced data, or called `wandb.Run.finish()`.                                 |
| `Killed`   | The run was forcibly stopped before it could finish.                                                 |
| `Running`  | The run is still running and has recently sent a heartbeat.                                          |
| `Pending`  | The run is scheduled but not yet started (common in sweeps and Launch jobs).                         |

### Run states in sweeps

When runs are part of a [sweep](/models/sweeps/), their states behave independently from the sweep's status. The following points describe how run states interact with sweeps:

* **Individual run states** reflect each run's execution status, such as `Running`, `Finished`, or `Failed`.
* **Sweep status** controls whether new runs are created, not how existing runs execute.
* Pausing or stopping a sweep doesn't affect already-running runs.
* Only canceling a sweep forcibly stops running runs (changes their state to `Killed`).

For a detailed explanation of how sweep and run statuses interact, see [Understanding sweep and run statuses](/models/sweeps/pause-resume-and-cancel-sweeps#understanding-sweep-and-run-statuses).

## View the state of a run

You can view a run's state programmatically with the Python SDK or interactively in the W\&B App. Choose the Python SDK to inspect or filter states across many runs at once. Choose the W\&B App to check a single run interactively.

<Tabs>
  <Tab title="Python SDK">
    Use the `state` property of the [`wandb.Api.Run`](/models/ref/python/public-api/runs) object to access the current state of a run.

    The following code snippet retrieves and prints the state of all runs in a specified project. Copy the following code snippet into your Python environment. Replace `[ENTITY]` with your W\&B entity name and `[PROJECT]` with your W\&B project name:

    ```python theme={null}
    import wandb

    api = wandb.Api()

    runs = api.runs(path="[ENTITY]/[PROJECT]")

    # Access run object's properties
    for run in runs:
        print(f"Run: {run.name}")
        print(f"Run state: {run.state}")
        print()
    ```

    You can apply different filters to retrieve runs from your projects based on different criteria. See [Filter runs](/models/runs/filter-runs) to learn more about filtering runs programmatically.
  </Tab>

  <Tab title="W&B App">
    View the state of a run from the W\&B App:

    1. Navigate to your W\&B project.
    2. Select the **Workspace** or **Runs** tab from the project sidebar.
    3. Search or scroll to the run you want to view.
    4. Select the run to open the run overview page.
    5. Choose the **Overview** tab.

    The current state of the run appears next to the **State** field.
  </Tab>
</Tabs>