> For the complete documentation index, see [llms.txt](https://manual.firstresonance.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://manual.firstresonance.io/workflow-builder/testing-a-flow.md).

# Testing a Flow

How to test your workflow

There are a couple of ways to test your workflow.

## Manual Run

You can manually trigger your workflow by using the `Run` button at the bottom left hand side of the Workflow Builder.

<figure><img src="https://3615148728-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LkRqYp6lJhwxjYdzYG8%2Fuploads%2Fgit-blob-c81af4450508dcf39b6e091ab1a1706e6933f5b6%2Fimage.png?alt=media" alt=""><figcaption></figcaption></figure>

The `Run history` tab will display previous test and live runs of the workflow.

<figure><img src="https://3615148728-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LkRqYp6lJhwxjYdzYG8%2Fuploads%2Fgit-blob-e61e09fe435a85b65fe07850a8d27d2ff0831d6b%2Fimage.png?alt=media" alt=""><figcaption></figcaption></figure>

## Live Execution

The `Live` button on the `Run history` will display all live executions of the workflow.

The recommended method for testing is to use a live execution. If your workflow is triggered off a certain event in ION, open up ION in a separate tab and initiate the event. For example, if you have a flow that this triggered when a purchase order is created, then every time you create a purchase order you will see an execution of the flow in the Workflow Builder.

<figure><img src="https://3615148728-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LkRqYp6lJhwxjYdzYG8%2Fuploads%2Fgit-blob-b76ca2e1b4b3f4cd4ad871a2308f29d14979159a%2Fimage.png?alt=media" alt=""><figcaption></figcaption></figure>

You can click through each step to display the output and logs.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://manual.firstresonance.io/workflow-builder/testing-a-flow.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.