# Working with run logs ## Introduction Having accessed the `process flow run logs` page, the `active` tab displays active and previous process flow runs. These are listed chronologically based on the run start time:

At a glance, you can see the outcome of a run, the start date/time, the duration, how the run was triggered and whether there were any warnings. You can also access [additional options](#additional-options) for detailed logs, and more. By default, logs are displayed for the last seven days. You can change this using the associated date filter - here, you can clear all [filters](#filters) to show [all available logs](#log-retention), or add rules to apply a new [date/time range](#finding-logs-by-date):

{% hint style="info" %} Click the name of a process flow to access its setup. {% endhint %} {% hint style="info" %} If a process flow is running, it is displayed with a 'stop' button that you can use to [stop the run](https://doc.wearepatchworks.com/product-documentation/process-flows/managing-process-flows/stopping-a-running-process-flow). {% endhint %} ### Need to know * Run logs are retained for 7 days. * Payloads are retained for 72 hours. * Payloads are stored in AWS S3 (eu-west-2 London). * Payloads are encrypted during pull/push operations (HTTPS, TLS 1.2/1.3). * There is a limit on the number of process flow runs that can be started per minute. This limit varies according to your subscription tier - please see [Core subscription tiers](https://doc.wearepatchworks.com/product-documentation/getting-started/core-subscription-tiers) for information. ## Searching run logs If you're looking for a specific log, you can use the search field to search by `flow run id` or by process flow name:

#### Searching by flow run ID If you want to find logs for a specific `flow run id`, type the full id into the search field - for example:

You must enter the id in full; partial elements are not matched. {% hint style="info" %} A `flow run id` search is not case sensitive. Entering `01j6errxr432r4k4dh41y5ttpc` is the same as `01J6ERRXR432R4K4DH41Y5TTPC` or `01J6eRRxR432r4K4DH41Y5ttPC`. {% endhint %} #### Searching by flow name If you want to find logs for a process flow that you only know by name, type any part of the name into the `search` field - for example:

You can enter as much or as little of the name as you like. {% hint style="info" %} A flow name search is not case sensitive - entering `CHECK` is the same as `check` or `Check`. {% endhint %} ## Filtering run logs Use filters to refine the list based on the value associated with a particular column. Currently, you can filter logs by: * Started at date * Trigger (schedule, manual, API, etc.) * Has warnings * Status To define a filter, click the filter icon associated with a column - for example:

...then make selections from the options provided - for example:

The date filter displays date/time rule pickers:

## Understanding the run status The status of a run will be one of the following:

Status	Summary
Success	The process run was completed success without errors.
Partial success	The process flow run was completed successfully however, at least one failed payload was removed.
Failure	The process run did not complete due to errors. See Handling flow run failures for more information.
Retried	The failed run has been retried. The colour associated with this status correlates to the outcome of that retry: Blue. The retry is running now (look for a correlating `running` entry in the logs) Green. The retry completed successfully (look for a correlating `success` entry in the logs). Red. The retry failed (look for a correlating `failure` entry in the logs).
Stopped	The process flow was stopped manually.
Running	The process flow is currently running. If you have lots of running flows that must be stopped, you can use a bulk action to stop all current runs.

## Handling flow run warnings If warnings are given during a run (be it failed or successful), the entry is shown with an icon in the `Has warnings` column - for example:

If the run [failed](#handling-flow-run-failures), review [detailed logs](https://doc.wearepatchworks.com/product-documentation/process-flows/error-reporting-and-exception-handling/run-logs-and-queue/working-with-run-logs/viewing-detailed-logs-for-a-flow-run) to check these warnings, then make any necessary changes to your process flow. If the run succeeded, you should still review the logs for warnings in case the issue causes a future failure. ## Handling flow run failures A process flow run may fail for any number of reasons - for example, perhaps a connected system is unavailable or expected data schemas/types have changed. When a process flow run fails, its status is set to `failure` and an expandable arrow is shown to the left of the entry - click this arrow to view a summary of why the failure occurred. For example:

Having confirmed/resolved any issues with a failed flow run, you can use the [retry option](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) to try again or - if there are lots of failures - use a [bulk action](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-or-stopping-multiple-flow-runs-bulk-actions) to retry all current failures. ## Aditional options Each log entry has an ellipses icon, with access to additional options:

From here you can:

Option	Summary
`View logs`	Access more insights and detailed logs for this run. For more information, please see Viewing logs.
`View logs (classic)`	If you prefer to work with 'original style' logs, you can access them from here. For more information, please see Viewing logs (classic).
`Download logs`	Use this option to download detailed logs in CSV format. For more information, please see Downloading run logs.
`Retry the flow run`	Use this option to retry a process flow run that previously failed. For more information, please see Retrying a failed process flow run.

## Deleted flow versions If a flow version has been run and subsequently deleted, existing run logs for the deleted version are retained as per [standard retention rules](#need-to-know). {% hint style="info" %} Perhaps the most typical scenario for [deleting a flow version](https://doc.wearepatchworks.com/product-documentation/process-flows/building-process-flows/process-flow-versioning) is where a later iteration of the flow is deployed, and the now `inactive` version is removed as part of a 'housekeeping' exercise. {% endhint %} This means you can view run log information for the deleted flow, but the flow version itself cannot be accessed. For clarity, you will see two indications that the flow version associated with a run has been deleted. First, you'll see a `(deleted)` tag after the flow name in the `process flow run logs` list. For example:

If you go on to view logs for one of these entries, you'll see a warning message against the flow version. For example:

## Related information * [Viewing logs](https://doc.wearepatchworks.com/product-documentation/process-flows/error-reporting-and-exception-handling/run-logs-and-queue/working-with-run-logs/viewing-detailed-logs-for-a-flow-run) * [Viewing logs (classic)](https://doc.wearepatchworks.com/product-documentation/process-flows/error-reporting-and-exception-handling/run-logs-and-queue/working-with-run-logs/viewing-logs-classic) * [Downloading run logs](https://doc.wearepatchworks.com/product-documentation/process-flows/error-reporting-and-exception-handling/run-logs-and-queue/working-with-run-logs/downloading-run-logs) * [Retrying a failed process flow run](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) * [Working with your run queue](https://doc.wearepatchworks.com/product-documentation/process-flows/error-reporting-and-exception-handling/run-logs-and-queue/working-with-your-run-queue) * [Email notifications for failed process flow runs](https://doc.wearepatchworks.com/product-documentation/process-flows/error-reporting-and-exception-handling/email-notifications-for-failed-process-flow-runs)