> For the complete documentation index, see [llms.txt](https://docs.locoia.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.locoia.com/automation/flow-debugger/run-flows-again.md).

# Run Flows again

With "Run again" you can re-run a flow with the same webhook input as the original Flow Run

In the Flow Debugger you can directly re-run previous Flow Runs without having to go back to the Flow Builder itself or sending another [Webhook to trigger the Flow](/connectors/helpers/webhook-helper.md) by using the **Run again** button which appears above the steps of a Flow Run.

When re-running a Flow Run which doesn't use a webhook, it behaves in the same way as manually running a Flow from the Flow Builder, as there's no specific input needed. For Flows that use a webhook however, the **webhook input of the re-ran flow will be used for the new Flow Run**.

Also, the new Flow Run will be marked as a re-run and link to the original Flow Run.

![](https://291121471-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McrRFZHYH27bqKzOVDd%2Fuploads%2Flj6t4gMCCSghUoqkUrmW%2Fimage.png?alt=media\&token=52134068-4e2b-4fe0-a680-2339004c897c)

{% hint style="info" %}
When re-running a Flow that uses an [async webhook](/connectors/helpers/webhook-helper.md#async-webhook), the re-run will be ran right away as a regular webhook instead.
{% endhint %}


---

# 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://docs.locoia.com/automation/flow-debugger/run-flows-again.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.