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

# Running

> A run is a single execution of a workflow.

Once a workflow is built, you can run it manually at any time, schedule it to run automatically, or run it as a batch across multiple items. Every run is logged in full.

## Run types

| Type              | When to use                                                    |
| ----------------- | -------------------------------------------------------------- |
| **Manual run**    | You trigger the run yourself, on demand                        |
| **Scheduled run** | Felix triggers the run automatically at a set time or interval |
| **Batch run**     | One run processes multiple items through the workflow          |

Most workflows start as manual runs while you're testing. Once you're confident in the output, switch to scheduled or batch depending on how the workflow is used.

## Run history

Every run is saved to your workflow's run history. From the run history you can see the status of every run, open any run to view the full step-by-step log, download output files, and re-run a workflow with the same input.

## When a run is paused

If a workflow includes a Human Checkpoint, the run pauses at that step and waits for input. Felix notifies the person assigned to the checkpoint. There is no timeout — a paused run waits indefinitely until a response is provided.

## When a run fails

Felix logs exactly which step failed and why. Common causes:

* **Connector not authorised** — re-authenticate from **Settings → Connectors**
* **Missing input** — an earlier step produced no output for the failed step to work with
* **Step description too vague** — update the description and run again

You can re-run from the failed step without re-running the entire workflow.

## Tips

* **Test manually before scheduling.** Run the workflow once with a real input to confirm the output is correct.
* **Use batch runs for volume.** If you're processing more than a handful of items, a batch run is more efficient.
* **Check run history regularly.** Scheduled and batch runs happen without your involvement — review the logs periodically.

<CardGroup cols={3}>
  <Card title="Manual Runs" icon="play" href="/docs/running/one-off">
    Trigger a run on demand
  </Card>

  <Card title="Scheduled Runs" icon="clock" href="/docs/running/scheduled">
    Run automatically
  </Card>

  <Card title="Batch Runs" icon="layer-group" href="/docs/running/batch">
    Process multiple items
  </Card>
</CardGroup>