# Runs

Congratulations on having a workflow that's ready to run! Here's some basic information and suggestions on starting, viewing, and managing your runs.

### Test runs

If you're still validating your workflow, click `Start a test run` in the `Editor` tab to run your workflow all the way through. Test runs are the same as real runs, but you'll select existing data to use (e.g. an existing row in a spreadsheet) rather than waiting for a trigger.

Testing is free in Relay.app, with reasonable fair use limits. [Learn more about testing.](https://docs.relay.app/running-workflows/testing)

You'll see a summary of how many AI credits a step would have used at the top of the run once it's complete.

<figure><img src="https://647519108-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXkKoEy3xMIYaIwd4mRAB%2Fuploads%2Fgit-blob-49afa89a050928b27cd11169664e6d0c637e1f54%2Fimage.png?alt=media" alt=""><figcaption><p>Test runs (as well as step tests) don't cost AI credits. You'll see what it would have cost as a real run at the top of the run.</p></figcaption></figure>

To be able to start test runs, you'll need to publish any unpublished changes to your workflow.

### Runs tab

To see your workflow's active runs, click on the `Runs` tab at the top of the screen. Each run is a specific instance of your workflow.

<figure><img src="https://647519108-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXkKoEy3xMIYaIwd4mRAB%2Fuploads%2Fgit-blob-1782bf467e6a29f232c8cd7e91d9e2245ca2e723%2Fimage.png?alt=media" alt=""><figcaption><p>Runs tab</p></figcaption></figure>

Runs can be in several states. You'll see these states grouped in sections in the `All runs` list in the left navigation.

* Pending: Runs that haven't started yet, like a large batch still processing
* Running now: Runs that are actively working on the latest step
* Issues: Runs that are paused due to errors
* Action required: Runs that require a human-in-the-loop action, like entering data or approving that it can continue
* Waiting: Runs in a waiting state, for example due to a wait step or being manually paused
* Completed: Runs that have fully completed
* Trash: Deleted runs, which can be restored for 30 days before being permanently deleted

<figure><img src="https://647519108-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXkKoEy3xMIYaIwd4mRAB%2Fuploads%2Fgit-blob-4a1a89b60c1cd392cdd9b81a4b032b0f633d34b2%2Fimage.png?alt=media" alt=""><figcaption><p>Run view with some runs in an error state, waiting for human action, and completed.</p></figcaption></figure>

### Run actions

You can take different actions on runs based on their state:

* Pause: Stop all activity on a run until it's manually unpaused
* Retry failed steps: Rerun steps with errors to see if any recent updates to the workflow, or transient errors from the integration, have been resolved
* Replay: Start a new run using the same data as the selected run
* End: Make the run end right away, even if not all steps have completed
* Delete: They'll be in the trash for 30 days

Some sections will let you take these actions in bulk. For example, you can `Retry all failed steps` for all runs in the `Issues` section.

### Freezing runs

If you need to immediately stop the activity of a workflow, say because you have many active runs and you realize they all need to be stopped, look for the `Freeze all runs` button in the top right menu of the workflow or any run.

Freezing runs means:

* No new runs will be generated, even if your trigger conditions are matched
* All runs will immediately stop processing

While runs are frozen, you'll be able to delete them.

When you unfreeze, any active runs will continue again, and if there's a queue of missed trigger items, new runs will be created for them.

<figure><img src="https://647519108-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXkKoEy3xMIYaIwd4mRAB%2Fuploads%2Fgit-blob-28842e1181403be550719daf279bcc2b6b0815a0%2Fimage.png?alt=media" alt=""><figcaption><p>Freeze all runs: Your workflow's emergency "Wait, stop!" button</p></figcaption></figure>
