> For the complete documentation index, see [llms.txt](https://doc.wearepatchworks.com/product-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.wearepatchworks.com/product-documentation/process-flows/error-reporting-and-exception-handling/run-logs-and-queue/working-with-run-logs/handling-failed-process-flow-runs/retrying-a-failed-process-flow-run.md).

# Retrying a failed process flow run

## Introduction

If a process flow run fails for any reason, it's displayed in [run logs](/product-documentation/process-flows/error-reporting-and-exception-handling/run-logs-and-queue/working-with-run-logs/viewing-detailed-logs-for-a-flow-run.md) with a `failure` status - for example:&#x20;

<div align="left"><figure><img src="/files/wOjGUoJ6zTTymB8UFOvt" alt=""><figcaption></figcaption></figure></div>

You can retry a failed run individually (as detailed here) or, for multiple failures, you can use a [bulk action](/product-documentation/process-flows/error-reporting-and-exception-handling/run-logs-and-queue/working-with-run-logs/handling-failed-process-flow-runs/retrying-or-stopping-multiple-flow-runs-bulk-actions.md).

## Need to know

Please see [Handling failed process flow runs](/product-documentation/process-flows/error-reporting-and-exception-handling/run-logs-and-queue/working-with-run-logs/handling-failed-process-flow-runs.md#need-to-know) for points to consider before retrying a failed flow run.

## The steps

{% stepper %}
{% step %}
**Access your run logs**&#x20;

Log in to the [Patchworks dashboard](https://app.wearepatchworks.com/) and [access your run logs & queue](/product-documentation/process-flows/error-reporting-and-exception-handling/run-logs-and-queue.md#accessing-your-run-logs-and-queue-page) - ensure the `active` tab is selected.
{% endstep %}

{% step %}
**Select the retry option**

Click the ellipses icon to access additional options for the log entry, then select the `retry flow run` option. For example:

<div align="left"><figure><img src="/files/WEa9bFtrUX5s2NAUhvY5" alt=""><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}
**Confirm the retry operation**

When prompted, confirm that you want to proceed:

<div align="left"><figure><img src="/files/yvdpAVeAJIKD3pFtDPM1" alt=""><figcaption></figcaption></figure></div>
{% endstep %}
{% endstepper %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://doc.wearepatchworks.com/product-documentation/process-flows/error-reporting-and-exception-handling/run-logs-and-queue/working-with-run-logs/handling-failed-process-flow-runs/retrying-a-failed-process-flow-run.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
