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

# Run Statuses

> This page describes the different statuses that appear when running scenarios in Scenario Builder

## Overview

When you run a scenario in Scenario Builder, it progresses through several stages. Each stage has a status that indicates the current state of your run. This page explains what each status means and what actions you should take.

## Build Statuses

### Draft

Your scenario has been created but not yet submitted for building. This is the only point at which you can still modify scenario inputs, via the template files.

### Building

The model is being built from your scenario inputs. This process validates and assembles all the data required for the optimization run.

### Build Complete

The model has been built successfully and is ready to proceed to the solve stage.

### Failed

The model build did not complete successfully. This typically occurs when:

* Scenario inputs could not be assembled or validated correctly
* There are technical issues with data processing

**What to do:** This is a technical/backend issue. Contact [support@transitionzero.org](mailto:support@transitionzero.org) for assistance.

## Solve Statuses

### Solving

The optimization solver is running to find the optimal solution for your scenario.

### Solve Complete

The solver has successfully completed and found a solution. The run will proceed to process and save the results.

### Queued

Large models require additional compute capacity. Your solve is queued and will start automatically. This may take a few minutes.

### Infeasible

The model has been built successfully, but the solver determined that there is no possible solution to satisfy all the constraints.

**What to do:** This is a user issue. Check for conflicting inputs and re-run the model. Common causes include:

* Conflicting constraints (e.g., high demand growth with limited generation capacity)
* Overly strict emissions targets
* Conflicting targets that cannot be met simultaneously
* Insufficient build rates or potentials for required technologies

For more detailed guidance on resolving infeasibilities, see our [Understanding Infeasibilities](/platform/infeasibilities) documentation.

### Failed

The optimization run failed for a technical reason other than infeasibility. This can occur due to:

* Solver errors
* Timeout issues
* Other technical problems during the solve process

**What to do:** This is a technical/backend issue. Contact [support@transitionzero.org](mailto:support@transitionzero.org) for assistance.

## Results Statuses

### Finishing Up

The solve was completed successfully, and the results are being processed and saved.

### Done

The run has completed successfully. All results have been processed and saved, and you can now view and analyze them.

### Failed

The solve was completed, but the results could not be processed and saved.

**What to do:** This is a technical/backend issue. Contact [support@transitionzero.org](mailto:support@transitionzero.org) for assistance.

## Summary

| Status             | Description                                                                                                                   |
| ------------------ | ----------------------------------------------------------------------------------------------------------------------------- |
| **Draft**          | Scenario is created but not submitted; inputs can still be modified via template files.                                       |
| **Building**       | The model is being built, validating and assembling all required data.                                                        |
| **Build Complete** | The model has been built successfully and is ready for the solve stage.                                                       |
| **Solving**        | The optimization solver is running to find the optimal solution.                                                              |
| **Solve Complete** | The solver found a solution and is proceeding to process results.                                                             |
| **Queued**         | The solve is waiting for compute capacity and will start automatically. Large scenarios may be queued for an extended period. |
| **Infeasible**     | No possible solution satisfies all constraints; requires user adjustment of inputs.                                           |
| **Finishing Up**   | The solve was successful, and results are being processed and saved.                                                          |
| **Done**           | The run is complete, and results are ready for viewing and analysis.                                                          |
| **Failed**         | A technical/backend error occurred during building, solving, or saving results.                                               |