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

# Runs

> See what a workflow did each time it ran, and troubleshoot failed steps.

Each time a trigger fires, Yorlet records a **workflow run**. Use runs to confirm a workflow is doing what you expect, and to see why a step failed.

## View recent runs

Open a workflow from the [Workflows page](https://dashboard.yorlet.com/workflows). The **Recent runs** section lists every run for that workflow.

The table shows:

* **Status** — **Running**, **Succeeded**, or **Failed**.
* **Run** — the run ID.
* **Steps** — how many steps ran. If any failed, the count includes how many failed.
* **Created** — when the run started.

<Note>
  A workflow that is **Draft** or **Inactive** will not create new runs. Publish or click **Activate** first. See [Create a workflow](/business-automation/workflows/create-a-workflow).
</Note>

## Open a run

Click a run to open its detail page. The page is titled **Workflow run** and has three sections:

* **Overview** — **Status**, **Started**, and **Steps**.
* **Trigger payload** — the data that started the run, such as the event and the record, or the API input.
* **Steps** — each step that ran, in order.

If the run failed, a **Run failed** banner appears at the top.

## Step results

Each step shows the action name, or **Condition** / **For each** for logic steps, and a status:

* `succeeded` — the step completed.
* `failed` — the step stopped with an error.
* `skipped` — the step did not run, for example because the workflow took the other branch.

Condition steps also show a `true branch` or `false branch` badge for the path they took. Loop items show an `Item {n}` badge for each iteration.

When a step succeeded, expand **Output** to see what it created or returned — for example the task or invoice ID.

If no steps ran, the page shows **No steps were executed.** That usually means the workflow has no steps after the trigger.

## Troubleshoot a failed run

When a run is **Failed**, open it and find the first step with status `failed`. The step shows an error explaining why.

Typical causes:

* A required field was empty, or a [variable](/business-automation/workflows/variables) did not resolve — for example `{{ trigger.object.customer }}` when the trigger record has no customer.
* A broken reference, shown as a chip in the builder after you removed an earlier step.
* A **For each** array longer than 50 items.
* A **Send letter** step where the recipient is missing a name or address, or your account is missing a return address.
* An action for a product that is no longer enabled, such as Letters or Maintenance.

To fix it, follow these steps:

1. Open the workflow and click **Edit workflow**.
2. Correct the step — fill in the missing field, repair the variable, or add an [If / else](/business-automation/workflows/conditions-and-loops) so the action only runs when the data is present.
3. Click **Publish**.

The failed run is not replayed. The workflow will use your changes the next time the trigger fires.