Run Failures

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:

Language	Set & Continue	Immediate Exit
Node.js	process.exitCode = 1	process.exit(1)
Java	❌	System.exit(1)
C#	Environment.ExitCode = 1	Environment.Exit(1)
PHP	❌	exit(1) or die(1)

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 [email protected] 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 [email protected].

Failed (Timeout)

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