> For the complete documentation index, see [llms.txt](https://docs.pandium.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pandium.com/getting-started/anatomy-of-an-integration/run-failures.md).

# Run Failures

Learn about Pandium run failures, their causes (integration, refresh, platform, timeout), and how to troubleshoot or report issues effectively.

### What Are Run Failures?

In the instance that an error occurs during a sync, there are four possible status that will be reflected for a run:

* Failed (Integration Issue)
* Failed (Refresh)
* Failed (Platform Issue)
* Failed (Timeout)

#### Integration Issues

If something fails inside your integration code, in order to properly reflect a failed status, it is the responsibility of the integration development team to exit the process with a failed status code. Below are some examples codes that can be used for different languages:

<table><thead><tr><th>Language</th><th width="223.78125">Set &#x26; Continue</th><th>Immediate Exit</th></tr></thead><tbody><tr><td>Node.js</td><td><code>process.exitCode = 1</code></td><td><code>process.exit(1)</code></td></tr><tr><td>Java</td><td>❌</td><td><code>System.exit(1)</code></td></tr><tr><td>C#</td><td><code>Environment.ExitCode = 1</code></td><td><code>Environment.Exit(1)</code></td></tr><tr><td>PHP</td><td>❌</td><td><code>exit(1)</code> or <code>die(1)</code></td></tr></tbody></table>

**Refresh Failures**

There may be instances where a run fails due to a error during the refresh process. Disconnecting and reconnecting the tenant will typically help resolve these types of failures. However, if you continue to experience refresh failures even after performing these initial troubleshooting steps, please reach out to your Technical Account Manager or submit a support request to <support@pandium.com> to further assist with investigatory efforts.

**Platform Issue**

There may be times when a failure is the result of an internal issue impacting Pandium's infrastructure. Depending on the severity, the Pandium team will report any known errors to our status page - <https://status.pandium.com/>. However, it's possible the platform failure is isolated to a specific tenant(s). If no status related to platform failures is visible on the Pandium status page, please reach out to your Technical Account Manager or submit a support request to <support@pandium.com>.

**Failed (Timeout)**

Timeout errors will occur when the tenant run job exceeds the ten minute limit.<br>


---

# 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.pandium.com/getting-started/anatomy-of-an-integration/run-failures.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.