Skip to main content

Understanding Error status cases

Errors status#

There are different types of error:

  • HTTP responses: In general, codes in the 2xx range indicate success, codes in the 4xx range indicate an error that fails given the information provided, and codes in the 5xx range indicate an error with our services. See the Errors chapter for more information
  • Errors detailed in statuses which allow to target the cause of the error and to be able to react accordingly.

Note the connection status is deduced from the statuses of its channels, following these rules:

connection statuschannels statuses
SUCCESSAll channels of the connection are SUCCESS.
PARTIAL_SUCCESSOne channel is SUCCESS and other channel is PARTIAL_SUCCESS, or both are PARTIAL_SUCCESS.
FAILEDAt least one of the channels is in a state requiring an action.
RUNNINGAt least one of the channels is RUNNING. This status has priority over FAILED (see examples below).
CLOSEDThe connection is closed. All accounts are CLOSED. All channels are CLOSED. A channel cannot get CLOSED status independently.
NONEManual connections only. A manual connection do not have any channel.

Examples:

  • connection A
    • channel EMBEDDED SUCCESS
    • channel REDIRECT TOKEN_EXPIRED
    • => connection A has status FAILED
  • connection B
    • channel EMBEDDED RUNNING
    • channel REDIRECT TOKEN_EXPIRED
    • => connection B has status RUNNING
  • connection C
    • channel EMBEDDED SUCCESS
    • channel REDIRECT PARTIAL_SUCCESS
    • => connection C has status PARTIAL_SUCCESS

These statuses are present at the API commands and events level. In the API, they can take different values depending on the context (related objects):