We classify connection job failures into three categories based on responsibility for resolution:

  • Leen: Issues originating from Leen’s infrastructure or code. We prioritize these failures and work to resolve them as quickly as possible.
  • Customer: Failures due to invalid or expired credentials. Customer must update credentials to resolve the failure.
  • Vendor: Failures caused by the Vendor’s API, such as network issues or 5xx errors. These failures are often temporary and may resolve automatically in subsequent runs.

How to find Connection Health

You can use List Connections or Get Connection by ID. Here is an example response with connection health value:

{
    ...
    "health": {
        "name": "HEALTHY",
        "status": "HEALTHY",
        "description": "Connection is healthy",
        "resolution_owner": "LEEN",
        "details": null
    }
}

Connection Health Statuses

NameStatusResolution OwnerDescription
HEALTHYHEALTHYLEENConnection is healthy
EXECUTION_TIMEOUTUNHEALTHYLEENExecution timeout
RATE_LIMIT_EXCEEDEDUNHEALTHYLEENRate limit exceeded
VENDOR_CLIENT_ERRORUNHEALTHYLEENVendor returned a 4xx client error
INTERNAL_ERRORUNHEALTHYLEENInternal error
VENDOR_SERVER_ERRORUNHEALTHYVENDORVendor returned a 5xx server error
UNAUTHORIZEDUNHEALTHYCUSTOMERConnection is unauthorized