> 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.md).

# Run logs & queue

## Introduction

<figure><img src="/files/v2vleVgANKP10TYnfbkm" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Flow run details are available from the time you started running process flows. Logs are available as per a standard retention period (please see [Viewing 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) for details).
{% endhint %}

## Accessing your run logs & queue page

To access the run logs & queue page, follow the steps below.

{% stepper %}
{% step %}
**Select the run logs menu option**

Log in to the [Patchworks dashboard](https://app.wearepatchworks.com/) and select `run logs` from the left-hand navigation menu:

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

{% step %}
**Choose what to view**

Select the `active` tab to view active and previous flow runs, or the `queue` tab for pending runs:

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

## Related pages

* [Working with run logs](/product-documentation/process-flows/error-reporting-and-exception-handling/run-logs-and-queue/working-with-run-logs.md)
* [Working with your run queue](/product-documentation/process-flows/error-reporting-and-exception-handling/run-logs-and-queue/working-with-your-run-queue.md)


---

# 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.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.
