Run states
The following table describes the possible states a run can be in:| State | Description |
|---|---|
Crashed | Run stopped sending heartbeats in the internal process, which can happen if the machine crashes. |
Failed | Run ended with a non-zero exit status. |
Finished | Run ended and fully synced data, or called wandb.Run.finish(). |
Killed | Run was forcibly stopped before it could finish. |
Running | Run is still running and has recently sent a heartbeat. |
Pending | Run is scheduled but not yet started (common in sweeps and Launch jobs). |
Run states in sweeps
When runs are part of a sweep, their states behave independently from the sweep’s status:- Individual run states reflect each run’s execution status (Running, Finished, Failed, etc.)
- 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 cancelling a sweep forcibly kills running runs (changes their state to
Killed)
View the state of a run
Programmatically or interactively view a run’s state with the Python SDK or W&B App.- Python SDK
- W&B App
Use the You can apply different filters to retrieve runs from your projects based on different criteria. See Filter runs to learn more about filtering runs programmatically.
state property of the wandb.Api.Run 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 and paste the following code snippet into your Python environment. Replace the values enclosed in angle brackets (< >) with your own values: