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

# Working with Runs

> Review workflow runs, navigate between the Run list and the Editor, and inspect a past run on the canvas.

## Overview

A **run** is a single execution of a workflow. Each run is recorded independently of the live workflow definition, so you can review past runs, re-run them, and (when the live workflow has diverged from the version that produced a run) restore the workflow to that earlier version.

This page covers where to find runs, the Run list page, and how a run opens in the Workflow Editor.

***

## Run Statuses

Each run has one of the following statuses:

| Category | Status              | Meaning                                     |
| -------- | ------------------- | ------------------------------------------- |
| Active   | **Pending**         | Run is queued and waiting to start.         |
| Active   | **Running**         | Run is currently executing.                 |
| Active   | **Stopping**        | Stop was requested; run is winding down.    |
| Active   | **Scheduled**       | Run is scheduled for a future time.         |
| Terminal | **Completed**       | All nodes finished successfully.            |
| Terminal | **Partial Success** | Some nodes succeeded; some did not.         |
| Terminal | **Failed**          | Run finished with one or more failed nodes. |
| Terminal | **Stopped**         | Run was stopped before completion.          |
| Terminal | **Error**           | Run ended due to a platform error.          |

Active runs auto-refresh in the UI and are pinned to the top of run lists.

***

## Where to Find Runs

Runs surface in three places, each scoped differently:

* **Workspace Runs page** lists runs across all workflows in the current workspace.
* **Vault Runs page** lists runs across all workspaces in the vault.
* **Editor Runs sidebar** lists runs of the workflow you are currently editing. See [Navigating the Editor](./navigating-the-editor) for that view.

***

## The Run List Page

The Run list page (workspace or vault) displays one row per run.

Each row shows:

* **Run ID** and creation type (Manual, Scheduled, or API)
* **Status** with duration
* **Workflow name** (and workspace badge on the vault page)
* **Active machines** (only while the run is active)
* **Time** the run was created
* **Author**
* A **`...`** menu with per-row actions

You can filter and sort the list using:

* **Status tabs**: **All**, **Active**, **Completed**, **Failed**, **Stopped**
* **Recent Workflows**
* **Started By** (author)
* **Project**
* **Sort**: Newest first or Oldest first

### Per-Run Actions

Open the **`...`** menu on any row to:

* **View in Editor**: open the editor with this run loaded
* **View Details**: open a side panel with the run's metadata
* **Run Again**: start a new run using the same workflow version
* **Rename**: change the run name
* **Export IPs**: export the IP addresses used by the run
* **Create Workflow**: create a new workflow from the run's workflow version
* **Delete**: delete the run (only available for terminal runs)

***

## Opening a Run from the Run List

A run row has two distinct click targets that route you to the editor in different states:

* Clicking the **Run ID** opens the editor with this run loaded. The URL becomes `/editor/<workflow>?run=<runId>`.
* Clicking the **Workflow name** opens the live editor for that workflow with no run context.

Use the Run ID when you want to inspect what a specific run produced. Use the workflow name when you want to continue editing the workflow.

> **Tip** The same routing applies to **View in Editor** in the `...` menu, which opens the editor with the run loaded.

***

## Viewing a Run in the Editor

When you open a run in the editor (from the Run list, the **Runs History** sidebar, or by selecting a run anywhere else), a **Viewing run** banner appears at the top of the canvas.

The banner contains:

* A **status pill** that reads **Loading...**, **Running**, **Viewing run**, or **Viewing module run** (when the run was a module execution opened in the module editor) depending on the state
* A **Back to editor** button to exit run view and return to the live workflow
* A **Restore** button (only when the run uses a different workflow version, see below)

The editor behaves differently based on whether the run's workflow version matches the live one:

* **Same version as the live workflow**: the canvas stays editable. Run statuses and outputs overlay the nodes so you can inspect what each node produced.
* **Different version**: the canvas shows the run's historical workflow snapshot in read-only mode. **Restore** appears in the banner so you can replace the live workflow with this version.

> **Note** A different version means the workflow structure changed since the run executed. Position-only changes (moving nodes on the canvas) do not count as a different version.

For the steps to restore a workflow to a past run's version, see [Restore a Past Run's Version](./building-and-debugging-a-workflow#6-restore-a-past-runs-version) in Building and Debugging a Workflow.