# Your third-party systems go offline

## Scenario

There may be occasions where your systems go offline - perhaps due to a general outage, or any number of reasons.&#x20;

When this happens, syncing to these or downstream systems will be disrupted, resulting in errors reported in your Patchworks [run logs](https://doc.wearepatchworks.com/product-documentation/process-flows/error-reporting-and-exception-handling/run-logs-and-queue). Don’t be alarmed by these errors - they are to be expected, and can be resolved.&#x20;

## Solution

Once your systems are back online, edit any affected process flows and (temporarily) adjust any filter settings to cover the downtime period - then [run the process flow manually](https://doc.wearepatchworks.com/product-documentation/process-flows/managing-process-flows/initialising-a-process-flow-manually).

{% hint style="info" %}
Avoid deploying this change as it will affect any future runs.
{% endhint %}
