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

# Workflow runs

> Inspect run history, understand statuses, replay inputs, and cancel scheduled work.

A **workflow run** is one execution attempt created from trigger data. Each run
stores its input payload, status, node outputs and errors, and a snapshot of the
workflow graph selected when the run was queued.

## Open run history

WorkflowDog provides two views:

| View                        | Best for                                                         |
| --------------------------- | ---------------------------------------------------------------- |
| **Project → Workflow Runs** | Reviewing activity across every workflow in a project.           |
| **Editor → Run History**    | Inspecting runs and node-level results for the current workflow. |

Both views update active **Pending** and **Running** rows automatically.

The project view shows the workflow name, date, duration, status, and run
actions. The editor history lets you select a run and display its data directly
on the canvas.

## Run statuses

| Status        | Meaning                                                                      |
| ------------- | ---------------------------------------------------------------------------- |
| **Pending**   | Accepted and waiting for execution to start.                                 |
| **Scheduled** | Accepted for a future time and waiting in the queue.                         |
| **Running**   | The workflow runner has started processing the graph.                        |
| **Completed** | The runner finished the graph. One or more individual nodes may still error. |
| **Failed**    | The run could not execute or the workflow runner itself failed.              |
| **Cancelled** | An Editor cancelled the run while it was still Scheduled.                    |

<Warning>
  **Completed** does not mean every node succeeded. A completed run with an
  amber warning icon contains one or more node errors. Open the run and inspect
  the affected nodes.
</Warning>

Common run-level **Failed** reasons include:

* The workflow was paused.
* The project had no remaining run credits and no active usage billing.
* The project's payment state did not allow new usage.
* The execution worker encountered an unrecoverable error.

See [Troubleshoot workflow runs](/guides/troubleshooting-runs) for a diagnostic
flow.

## Inspect a run on the canvas

Select a row from **Run History** in the workflow editor. Node outputs and
errors become available for that run, and the editor offers two canvas modes.

<Tabs>
  <Tab title="Snapshot (Read-Only)">
    Shows the saved graph snapshot associated with the run. Use this mode to
    answer: “What graph actually ran?”

    The snapshot cannot be edited. It remains stable even after you change the
    current workflow.
  </Tab>

  <Tab title="Overlay">
    Keeps the current workflow graph editable while applying the selected run's
    results where node and handle identifiers still match.

    Use this mode to fix the current workflow while referring to a recent run.
    If nodes were deleted, replaced, or rewired after the run, some historical
    results may not line up with the current graph.
  </Tab>
</Tabs>

Use **Newer** and **Older** to move between the runs loaded by the editor. This
navigation operates on the latest 100 runs fetched for the workflow. Open the
history drawer and scroll when you need an older entry.

## Star an important run

Use the star action to mark an incident, representative payload, or run you
want to find again. Stars are stored with the run and are visible to project
members.

Starring does not change retention, execution, or billing.

## Re-run with the same trigger data

Choose **Re-run** to queue a new run using the selected run's saved trigger
payload.

<Warning>
  A re-run is not an exact replay of the historical snapshot. It uses the same
  trigger data against the workflow's **current saved graph**, then creates a
  new snapshot for that graph. Review unsaved changes and wait for **Saved**
  before re-running.
</Warning>

A re-run can also fail immediately when the workflow is paused, the project is
out of credits, or billing is invalid. It creates a separate history entry and
does not modify the original run.

## Cancel a scheduled run

Only a run in **Scheduled** status can be cancelled. Choose **Cancel Run** from
its actions.

Cancellation:

* Changes the run to **Cancelled**.
* Prevents the delayed execution from starting.
* Restores the run credit or usage charge reserved when the run was scheduled.

Pending and Running runs cannot be cancelled from the dashboard.

## Run history after deletion

Deleting a workflow removes its workflow graph, trigger configuration, event
sources, and snapshots. Project-level run records remain for usage tracking and
appear as **Deleted Workflow**.

<Note>
  A preserved run row from a deleted workflow cannot be re-run, and its
  historical canvas snapshot is no longer available. Deleting the entire project
  removes its run history.
</Note>

WorkflowDog currently does not expose a configurable run-history retention
setting in the dashboard.

## Troubleshooting

<AccordionGroup>
  <Accordion title="A run says Completed but shows errors">
    The workflow runner completed, but at least one node reported an error.
    Select the run, inspect the red or warning-marked nodes, and read their
    stored error messages.
  </Accordion>

  <Accordion title="Re-run used my newer workflow changes">
    This is expected. Re-run preserves the old trigger payload, not the old graph.
    Use **Snapshot (Read-Only)** to inspect the original graph and **Overlay** to
    repair the current one.
  </Accordion>

  <Accordion title="Cancel Run is not available">
    Cancellation is limited to Scheduled runs. A Pending or Running run has
    already moved beyond the cancellable delayed state.
  </Accordion>

  <Accordion title="The historical snapshot will not load">
    The snapshot can be unavailable if its workflow was deleted. Check the
    project-wide history for a **Deleted Workflow** label.
  </Accordion>
</AccordionGroup>