# Existing Connection Interruptions source: https://developer.mastercard.com/open-finance-au/documentation/errors/institutionerrors/connection-interrupt/existing-connection-interruptions/index.md The following errors occur when existing connection to a financial institution is down and the end user may experience failed attempt to add their bank accounts.​ * [101](https://developer.mastercard.com/open-finance-au/documentation/errors/institutionerrors/connection-interrupt/existing-connection-interruptions/index.md#101) * [102](https://developer.mastercard.com/open-finance-au/documentation/errors/institutionerrors/connection-interrupt/existing-connection-interruptions/index.md#102) * [104](https://developer.mastercard.com/open-finance-au/documentation/errors/institutionerrors/connection-interrupt/existing-connection-interruptions/index.md#104) * [105](https://developer.mastercard.com/open-finance-au/documentation/errors/institutionerrors/connection-interrupt/existing-connection-interruptions/index.md#105) * [905](https://developer.mastercard.com/open-finance-au/documentation/errors/institutionerrors/connection-interrupt/existing-connection-interruptions/index.md#905) * [906](https://developer.mastercard.com/open-finance-au/documentation/errors/institutionerrors/connection-interrupt/existing-connection-interruptions/index.md#906) * [907](https://developer.mastercard.com/open-finance-au/documentation/errors/institutionerrors/connection-interrupt/existing-connection-interruptions/index.md#907) * [908](https://developer.mastercard.com/open-finance-au/documentation/errors/institutionerrors/connection-interrupt/existing-connection-interruptions/index.md#908) * [910](https://developer.mastercard.com/open-finance-au/documentation/errors/institutionerrors/connection-interrupt/existing-connection-interruptions/index.md#910) * [911](https://developer.mastercard.com/open-finance-au/documentation/errors/institutionerrors/connection-interrupt/existing-connection-interruptions/index.md#911) * [970](https://developer.mastercard.com/open-finance-au/documentation/errors/institutionerrors/connection-interrupt/existing-connection-interruptions/index.md#970) * [971](https://developer.mastercard.com/open-finance-au/documentation/errors/institutionerrors/connection-interrupt/existing-connection-interruptions/index.md#971) * [2018](https://developer.mastercard.com/open-finance-au/documentation/errors/institutionerrors/connection-interrupt/existing-connection-interruptions/index.md#2018) * [418 and 419](https://developer.mastercard.com/open-finance-au/documentation/errors/institutionerrors/connection-interrupt/existing-connection-interruptions/index.md#418-and-419) * [575](https://developer.mastercard.com/open-finance-au/documentation/errors/institutionerrors/connection-interrupt/existing-connection-interruptions/index.md#575) * [579](https://developer.mastercard.com/open-finance-au/documentation/errors/institutionerrors/connection-interrupt/existing-connection-interruptions/index.md#579) * [580](https://developer.mastercard.com/open-finance-au/documentation/errors/institutionerrors/connection-interrupt/existing-connection-interruptions/index.md#580) ## 101 {#101} | Title | Details | |---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | **Error Code** | 101 | | **Remediation Category** | Retry Later | | **HTTP Status** | 500 | | **Data Connect Alert** | We're unable to establish a connection to your financial institution. Try again later or select another institution. (101) ![101](https://static.developer.mastercard.com/content/open-finance-au/uploads/101.png) | | **Error Message** | There is currently a problem with the connection to this financial institution and it's being worked on. Please try again later. | | **Common Causes** | This error usually happens when the bank updates its website or server. These changes can disrupt the connection between your app and the bank, requiring changes/updates to restore the original connection. | | **Troubleshooting Steps** | Submit a [support ticket](https://developer.mastercard.com/open-finance-au/documentation/support/index.md#create-a-support-case-in-scm) for troubleshooting. ​Simultaneously, Data Connect display alerts will automatically prompt the end user when they are in session to take suggested remediation action associated with this error. ​ Best Practice: Developers may prompt end users to log into their application to ensure the end users can take recommended action to resolve the issue. The end user will be prompted to login to their account directly at the institution's website and follow the instructions there to proceed. | | **Retriable by End User** | Yes, the end user will need to make 3-5 authentication attempts which will assist in the troubleshooting process. ​ | | **Access to Latest Data** | You will be unable to access the latest data for this user's account until the end user resolves the issue. | [Full Error List](https://developer.mastercard.com/open-finance-au/documentation/errors/error-list/index.md) ## 102 {#102} | Title | Details | |---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | **Error Code** | 102 | | **Remediation Category** | Retry Later | | **HTTP Status** | 500 | | **Data Connect Alert** | We're unable to establish a connection to your financial institution. Try again or select another institution. (102) ![102](https://static.developer.mastercard.com/content/open-finance-au/uploads/102-1.png) | | **Error Message** | Problem connecting to the institution. Wait a few minutes and try again. Submit a [support ticket](https://developer.mastercard.com/open-finance-au/documentation/support/index.md#create-a-support-case-in-scm) if the issue persists.​ | | **Common Causes** | This error usually happens when the bank updates its website or server. These changes can disrupt the connection between your app and the bank, requiring changes/updates to restore the original connection. | | **Troubleshooting Steps** | Submit a [support ticket](https://developer.mastercard.com/open-finance-au/documentation/support/index.md#create-a-support-case-in-scm) for troubleshooting. ​Simultaneously, Data Connect display alerts will automatically prompt the end user when they are in session to take suggested remediation action associated with this error. ​ Best Practice: Developers may prompt the end users to log into their application to ensure the end users can take recommended action to resolve the issue. | | **Retriable by End User** | Yes, the end user will need to make 3-5 authentication attempts which will assist in the troubleshooting process. ​ | | **Access to Latest Data** | You will be unable to access the latest data for this user's account until the end user resolves the issue. | [Full Error List](https://developer.mastercard.com/open-finance-au/documentation/errors/error-list/index.md) ## 104 {#104} | Title | Details | |---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | **Error Code** | 104 | | **Remediation Category** | Retry Later | | **HTTP Status** | 500 | | **Data Connect Alert** | We're unable to establish a connection to your financial institution. Try again or select another institution. (104) ![104](https://static.developer.mastercard.com/content/open-finance-au/uploads/104.png) | | **Error Message** | Temporary connection issue for the financial institution. Wait a few minutes and try again. Submit a [support ticket](https://developer.mastercard.com/open-finance-au/documentation/support/index.md#create-a-support-case-in-scm) if the issue persists. | | **Common Causes** | This error usually happens when the bank updates its website or server. These changes can disrupt the connection between your app and the bank, requiring changes/updates to restore the original connection. | | **Troubleshooting Steps** | Submit a [support ticket](https://developer.mastercard.com/open-finance-au/documentation/support/index.md#create-a-support-case-in-scm) for troubleshooting. ​Simultaneously, Data Connect display alerts will automatically prompt the end user when they are in session to take suggested remediation action associated with this error. ​Best Practice: Developers may prompt the end users to log into their application to ensure end users can take recommended action to resolve the issue. | | **Retriable by End User** | Yes, the end user will need to make 3-5 authentication attempts which will assist in the troubleshooting process. ​ | | **Access to Latest Data** | You will be unable to access the latest data for this user's account until the end user resolves the issue. | [Full Error List](https://developer.mastercard.com/open-finance-au/documentation/errors/error-list/index.md) ## 105 {#105} | Title | Details | |---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | **Error Code** | 105 | | **Remediation Category** | Retry Later | | **HTTP Status** | 500 | | **Data Connect Alert** | We're unable to establish a connection to your financial institution. Try again or select another institution. (105) ![105](https://static.developer.mastercard.com/content/open-finance-au/uploads/105.png) ​ | | **Error Message** | Institution's website is unavailable or intermittently available. Please retry again and if the problem persists, contact client support. | | **Common Causes** | This error usually happens when the bank updates its website or server. These changes can disrupt the connection between your app and the bank, requiring changes/updates to restore the original connection. | | **Troubleshooting Steps** | Submit a [support ticket](https://developer.mastercard.com/open-finance-au/documentation/support/index.md#create-a-support-case-in-scm) for troubleshooting. ​Simultaneously, Data Connect display alerts will automatically prompt the end user when they are in session to take suggested remediation action associated with this error. ​Best Practice: Developers may prompt the end users to log into their application to ensure the end users can take recommended action to resolve the issue. | | **Retriable by End User** | Yes, the end user will need to make 3-5 authentication attempts which will assist in the troubleshooting process. ​ | | **Access to Latest Data** | You will be unable to access the latest data for this user's account until the end user resolves the issue. | [Full Error List](https://developer.mastercard.com/open-finance-au/documentation/errors/error-list/index.md) ## 320 {#320} | Title | Details | |---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | **Error Code** | 320 | | **Remediation Category** | Retry Later | | **HTTP Status** | 500 | | **Data Connect Alert** | We're unable to establish a connection to your financial institution. Try again or select another institution. (320) | | **Error Message** | Problem connecting to the institution. Wait a few minutes and try again. Submit a [support ticket](https://developer.mastercard.com/open-finance-au/documentation/support/index.md#create-a-support-case-in-scm) if the issue persists.​ | | **Common Causes** | This error usually happens when the bank updates its website or server. These changes can disrupt the connection between your app and the bank, requiring changes/updates to restore the original connection. | | **Troubleshooting Steps** | Submit a [support ticket](https://developer.mastercard.com/open-finance-au/documentation/support/index.md#create-a-support-case-in-scm) for troubleshooting. ​Simultaneously, Data Connect display alerts will automatically prompt the end user when they are in session to take suggested remediation action associated with this error. ​ Best Practice: Developers may prompt the end users to log into their application to ensure the end users can take recommended action to resolve the issue. | | **Retriable by End User** | Yes, the end user will need to make 3-5 authentication attempts which will assist in the troubleshooting process. ​ | | **Access to Latest Data** | You will be unable to access the latest data for this user's account until the end user resolves the issue. | [Full Error List](https://developer.mastercard.com/open-finance-au/documentation/errors/error-list/index.md) ## 905 {#905} | Title | Details | |---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | **Error Code** | 905 | | **Remediation Category** | Retry Later | | **HTTP Status** | 500 | | **Data Connect Alert** | This attempt has been logged. The connection to this financial institution is currently in the second phase of the creation process. Please attempt to log-in (up to 5 attempts in a row if possible) in order to store all the additional authentication information needed, then try again in 2-3 days. (905) ![905](https://static.developer.mastercard.com/content/open-finance-au/uploads/905.png) | | **Error Message** | If user specific issue or FI partially broken or FI completely broken and it is existing. Programmed to gather login credentials questions on attempt.​ | | **Common Causes** | The connection to this financial institution is being fixed. If the customer can make multiple attempts to add it will assist in the fix process. | | **Troubleshooting Steps** | Submit a [support ticket](https://developer.mastercard.com/open-finance-au/documentation/support/index.md#create-a-support-case-in-scm) for troubleshooting. ​Simultaneously, Data Connect display alerts will automatically prompt the end user when they are in session to take suggested remediation action associated with this error. ​Best Practice: Developers may prompt the end users to log into their application to ensure the end users can take recommended action to resolve the issue. | | **Retriable by End User** | Yes, the end user will need to make 3-5 authentication attempts which will assist in the troubleshooting process. ​ | | **Access to Latest Data** | You will be unable to access the latest data for this user's account until the end user resolves the issue. | [Full Error List](https://developer.mastercard.com/open-finance-au/documentation/errors/error-list/index.md) ## 906 {#906} | Title | Details | |---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | **Error Code** | 906 | | **Remediation Category** | Retry Later | | **HTTP Status** | 500 | | **Data Connect Alert** | It requires at least 5 consecutive sign in attempts on your account to gather enough information to authenticate and create a new connection to your accounts. (906) ![906](https://static.developer.mastercard.com/content/open-finance-au/uploads/906.png) | | **Error Message** | If user specific issue or FI partially broken or FI completely broken and it is existing. Programmed to gather login credentials questions on attempt. | | **Common Causes** | The connection to this financial institution is being fixed. If the customer can make multiple attempts to add it will assist in the fix process. | | **Troubleshooting Steps** | Submit a [support ticket](https://developer.mastercard.com/open-finance-au/documentation/support/index.md#create-a-support-case-in-scm) for troubleshooting. ​Simultaneously, Data Connect display alerts will automatically prompt the end user when they are in session to take suggested remediation action associated with this error. ​Best Practice: Developers may prompt the end users to log into their application to ensure the end users can take recommended action to resolve the issue. | | **Retriable by End User** | Yes, the end user will need to make 3-5 authentication attempts which will assist in the troubleshooting process. ​ | | **Access to Latest Data** | You will be unable to access the latest data for this user's account until the end user resolves the issue. | [Full Error List](https://developer.mastercard.com/open-finance-au/documentation/errors/error-list/index.md) ## 907 {#907} | Title | Details | |---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | **Error Code** | 907 | | **Remediation Category** | Retry Later | | **HTTP Status** | 500 | | **Data Connect Alert** | This attempt has been logged. The connection to this financial institution is currently in the second phase of the creation process. Please attempt to log-in (up to 5 attempts in a row if possible) in order to store all the additional authentication information needed, then try again in 2-3 days. (907)​ ![907](https://static.developer.mastercard.com/content/open-finance-au/uploads/907-1.png) | | **Error Message** | If user specific issue or FI partially broken or FI completely broken. Existing code with OTP logging macro to gather HTML page info.​ | | **Common Causes** | This error usually happens when the bank updates its website or server. These changes can disrupt the connection between your app and the bank, requiring changes/updates to restore the original connection. | | **Troubleshooting Steps** | Submit a [support ticket](https://developer.mastercard.com/open-finance-au/documentation/support/index.md#create-a-support-case-in-scm) for troubleshooting. ​Simultaneously, Data Connect display alerts will automatically prompt the end user when they are in session to take suggested remediation action associated with this error. ​Best Practice: Developers may prompt end users to log into their application to ensure end users can take recommended action to resolve the issue. | | **Retriable by End User** | Yes, the end user will need to make 3-5 authentication attempts which will assist in the troubleshooting process. ​ | | **Access to Latest Data** | You will be unable to access the latest data for this user's account until the end user resolves the issue. | [Full Error List](https://developer.mastercard.com/open-finance-au/documentation/errors/error-list/index.md) ## 908 {#908} | Title | Details | |---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | **Error Code** | 908 | | **Remediation Category** | Retry Later | | **HTTP Status** | 500 | | **Data Connect Alert** | We ran into a connection issue, try again later or select another institution. (908) ![908](https://static.developer.mastercard.com/content/open-finance-au/uploads/908.png) | | **Error Message** | An error occurred in the institution script. Incorrect summary page created​. | | **Common Causes** | This error usually happens when the bank updates its website or server. These changes can disrupt the connection between your app and the bank, requiring changes/updates to restore the original connection. | | **Troubleshooting Steps** | Submit a [support ticket](https://developer.mastercard.com/open-finance-au/documentation/support/index.md#create-a-support-case-in-scm) for troubleshooting. ​Simultaneously, Data Connect display alerts will automatically prompt the end user when they are in session to take suggested remediation action associated with this error. ​Best Practice: Developers may prompt the end users to log into their application to ensure the end users can take recommended action to resolve the issue. | | **Retriable by End User** | Yes, the end user will need to make 3-5 authentication attempts which will assist in the troubleshooting process. ​ | | **Access to Latest Data** | You will be unable to access the latest data for this user's account until the end user resolves the issue. | [Full Error List](https://developer.mastercard.com/open-finance-au/documentation/errors/error-list/index.md) ## 910 {#910} | Title | Details | |---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | **Error Code** | 910 | | **Remediation Category** | Retry Later | | **HTTP Status** | 500 | | **Data Connect Alert** | We ran into a connection issue, try again later or select another institution. (910)​ ![910](https://static.developer.mastercard.com/content/open-finance-au/uploads/910.png) | | **Error Message** | Code used to indicate an FI is broken and currently being worked on. Can place this code while working on script to avoid unneeded tickets being submitted. E.g. Login URL hit is not possible through script or any type of posting is not possible. Login URL reloading multiple times OR FI is completely broken and need valid credentials to work further. | | **Common Causes** | This error usually happens when the bank updates its website or server. These changes can disrupt the connection between your app and the bank, requiring changes/updates to restore the original connection. | | **Troubleshooting Steps** | Submit a [support ticket](https://developer.mastercard.com/open-finance-au/documentation/support/index.md#create-a-support-case-in-scm) for troubleshooting. ​Simultaneously, Data Connect display alerts will automatically prompt the end user when they are in session to take suggested remediation action associated with this error. ​Best Practice: Developers may prompt the end users to log into their application to ensure the end users can take recommended action to resolve the issue. | | **Retriable by End User** | Yes, the end user will need to make 3-5 authentication attempts which will assist in the troubleshooting process. ​ | | **Access to Latest Data** | You will be unable to access the latest data for this user's account until the end user resolves the issue. | [Full Error List](https://developer.mastercard.com/open-finance-au/documentation/errors/error-list/index.md) ## 911 {#911} | Title | Details | |---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | **Error Code** | 911 | | **Remediation Category** | Retry Later | | **HTTP Status** | 500 | | **Data Connect Alert** | We ran into a technical issue, try again later or select another institution. (911) ![911](https://static.developer.mastercard.com/content/open-finance-au/uploads/911.png) | | **Error Message** | No accounts returned from script, due to a user specific issue or FI partially broken or FI completely broken and it is Existing. | | **Common Causes** | There is currently a problem with the connection to this financial institution and it's being worked on. Please try again later. | | **Troubleshooting Steps** | Submit a [support ticket](https://developer.mastercard.com/open-finance-au/documentation/support/index.md#create-a-support-case-in-scm) for troubleshooting. ​Simultaneously, Data Connect display alerts will automatically prompt the end user when they are in session to take suggested remediation action associated with this error. ​Best Practice: Developers may prompt the end users to log into their application to ensure the end users can take recommended action to resolve the issue. | | **Retriable by End User** | Yes, the end user will need to make 3-5 authentication attempts which will assist in the troubleshooting process. ​ | | **Access to Latest Data** | You will be unable to access the latest data for this user's account until the end user resolves the issue. | [Full Error List](https://developer.mastercard.com/open-finance-au/documentation/errors/error-list/index.md) ## 970 {#970} | Title | Details | |--------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | **Error Code** | 970 | | **Remediation Category** | Re-Authenticate or Provide Additional Information | | **HTTP Status** | 500 | | **Data Connect Alert** | No associated alert. | | **Error Message** | An error occurred in the financial institution connection. Submitting a support ticket is the recommended action. | | **Common Causes** | This error usually happens when the bank updates its website or server. These changes can disrupt the connection between your app and the bank, requiring changes/updates to restore the original connection. | | **Troubleshooting Steps** | Submit a [support ticket](https://developer.mastercard.com/open-finance-au/documentation/support/index.md#create-a-support-case-in-scm) for troubleshooting. ​Simultaneously, Data Connect display alerts will automatically prompt the end user when they are in session to take suggested remediation action associated with this error. ​Best Practice: Developers may prompt the end users to log into their application to ensure the end users can take recommended action to resolve the issue. | | **Suggested End User Message** | Suggest displaying this error message to your end users - "One or more parameters/headers in the request to Bank are invalid or missing. (Connection b/w us and bank is not working)​. " ​ | | **Retriable by End User** | No. ​ | | **Access to Latest Data** | You will be unable to access the latest data for this user's account until the issue is resolved. | [Full Error List](https://developer.mastercard.com/open-finance-au/documentation/errors/error-list/index.md) ## 971 {#971} | Title | Details | |---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | **Error Code** | 971 | | **Remediation Category** | Re-Authenticate or Provide Additional Information | | **HTTP Status** | 500 | | **Data Connect Alert** | No associated alert. | | **Error Message** | An error occurred in the financial institution connection. Submitting a support ticket is the recommended action. | | **Common Causes** | This error can occur for multiple reasons: * Can occur when the bank updates its website or server. These changes can disrupt the connection between your app and the bank, requiring changes/updates to restore the original connection. * Information provided by the end user during authentication is either incomplete or insufficient to link an account and access data. * Incorrect response to security questions, for example, incorrect security code or an expired security code due to time lapse. | | **Troubleshooting Steps** | Submit a [support ticket](https://developer.mastercard.com/open-finance-au/documentation/support/index.md#create-a-support-case-in-scm) for troubleshooting. ​Simultaneously, Data Connect display alerts will automatically prompt the end user when they are in session to take suggested remediation action associated with this error. ​Best Practice: Developers may prompt the end users to log into their application to ensure the end users can take recommended action to resolve the issue. | | **Retriable by End User** | Yes, the end user will be able to resume session, once the connection to the selected financial institutions is fixed. The end user may need to make several authentication attempts to assist in resolving the error. ​ ​ | | **Access to Latest Data** | You will be unable to access the latest data for this user's account until the issue is resolved. | [Full Error List](https://developer.mastercard.com/open-finance-au/documentation/errors/error-list/index.md) ## 972 {#972} | Title | Details | |---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | **Error Code** | 972 | | **Remediation Category** | Report or Escalate for Investigation | | **HTTP Status** | 500 | | **Data Connect Alert** | No associated alert. | | **Error Message** | This request is not allowed for Aggregator. | | **Common Causes** | This error can occur for multiple reasons: * Can occur when the bank updates its website or server. These changes can disrupt the connection between your app and the bank, requiring changes/updates to restore the original connection. * Information provided by the end user during authentication is either incomplete or insufficient to link an account and access data. * Incorrect response to security questions, for example, incorrect security code or an expired security code due to time lapse. | | **Troubleshooting Steps** | Submit a [support ticket](https://developer.mastercard.com/open-finance-au/documentation/support/index.md#create-a-support-case-in-scm) for troubleshooting. ​Simultaneously, Data Connect display alerts will automatically prompt the end user when they are in session to take suggested remediation action associated with this error. ​Best Practice: Developers may prompt the end users to log into their application to ensure the end users can take recommended action to resolve the issue. | | **Retriable by End User** | Yes, the end user will be able to resume session, once the connection to the selected financial institutions is fixed. The end user may need to make several authentication attempts to assist in resolving the error. ​ ​ | | **Access to Latest Data** | You will be unable to access the latest data for this user's account until the issue is resolved. | [Full Error List](https://developer.mastercard.com/open-finance-au/documentation/errors/error-list/index.md#institution-errors) ## 2018 {#2018} | Title | Details | |---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | **Error Code** | 2018 | | **Remediation Category** | Retry Later | | **HTTP Status** | 500 | | **Data Connect Alert** | We ran into a connection issue, try again later or select another institution. (2018)​ ![2018](https://static.developer.mastercard.com/content/open-finance-au/uploads/2018.png) | | **Error Message** | An error occurred in the institution script. No accounts returned from script.​ | | **Common Causes** | This error usually happens when the bank updates its website or server. These changes can disrupt the connection between your app and the bank, requiring changes/updates to restore the original connection. | | **Troubleshooting Steps** | Submit a [support ticket](https://developer.mastercard.com/open-finance-au/documentation/support/index.md#create-a-support-case-in-scm) for troubleshooting. ​Simultaneously, Data Connect display alerts will automatically prompt the end user when they are in session to take suggested remediation action associated with this error. ​Best Practice: Developers may prompt the end users to log into their application to ensure the end users can take recommended action to resolve the issue. | | **Retriable by End User** | Yes, the end user will need to make 3-5 authentication attempts which will assist in the troubleshooting process. ​ | | **Access to Latest Data** | You will be unable to access the latest data for this user's account until the end user resolves the issue. | [Full Error List](https://developer.mastercard.com/open-finance-au/documentation/errors/error-list/index.md) ## 418 and 419 {#418-and-419} | Title | Details | |---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | **Error Code** | 418 and 419 | | **Remediation Category** | Retry Later | | **HTTP Status** | 500 | | **Data Connect Alert** | No associated alert. | | **Error Message** | An error occurred in the financial institution connection. Submitting a support ticket is the recommended action. | | **Common Causes** | This error usually happens when the bank updates its website or server. These changes can disrupt the connection between your app and the bank, requiring changes/updates to restore the original connection. | | **Troubleshooting Steps** | Submit a [support ticket](https://developer.mastercard.com/open-finance-au/documentation/support/index.md#create-a-support-case-in-scm) for troubleshooting. ​Simultaneously, Data Connect display alerts will automatically prompt the end user when they are in session to take suggested remediation action associated with this error. ​Best Practice: Developers may prompt the end users to log into their application to ensure the end users can take recommended action to resolve the issue. | | **Retriable by End User** | Yes, the end user will need to make 3-5 authentication attempts which will assist in the troubleshooting process. ​ | | **Access to Latest Data** | You will be unable to access the latest data for this user's account until the end user resolves the issue. | [Full Error List](https://developer.mastercard.com/open-finance-au/documentation/errors/error-list/index.md) ## 575 {#575} | Title | Details | |---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | **Error Code** | 575 | | **Remediation Category** | Report or Escalate for Investigation | | **HTTP Status** | 500 | | **Data Connect Alert** | No associated alert. | | **Error Message** | Aggregation error. (575)​ | | **Common Causes** | This error usually happens when the bank updates its website or server. These changes can disrupt the connection between your app and the bank, requiring changes/updates to restore the original connection. | | **Troubleshooting Steps** | Submit a [support ticket](https://developer.mastercard.com/open-finance-au/documentation/support/index.md#create-a-support-case-in-scm) for troubleshooting. Simultaneously, Data Connect display alerts will automatically prompt the end user when they are in session to take suggested remediation action associated with this error. Best Practice: Developers may prompt the end users to log into their application to ensure the end users can take recommended action to resolve the issue. | | **Retriable by End User** | Yes, the end user will need to make 3-5 authentication attempts which will assist in the troubleshooting process. | | **Access to Latest Data** | You will be unable to access the latest data for this user's account until the end user resolves the issue. | [Full Error List](https://developer.mastercard.com/open-finance-au/documentation/errors/error-list/index.md) ## 579 {#579} | Title | Details | |---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | **Error Code** | 579 | | **Remediation Category** | Report or Escalate for Investigation | | **HTTP Status** | 500 | | **Connect Alert** | We were unable to establish a connection to your financial institution. Try again later or select another institution. (579)​. ![579](https://static.developer.mastercard.com/content/open-finance-au/uploads/579.png) | | **Error Message** | An error occurred in the financial institution connection. Submitting a support ticket is the recommended action.​ | | **Common Causes** | Typically, transactions are available on the financial institution, but data request failed to download transactions due to a blank page or some error on the website of the specific financial institution. This can also trigger a timeout error while waiting for a response from the website. As a result, connection is interrupted temporarily due to an unexpected error. ​ | | **Troubleshooting Steps** | Submit a [support ticket](https://developer.mastercard.com/open-finance-au/documentation/support/index.md#create-a-support-case-in-scm). | | **Retriable by End User** | No. | | **Access to Latest Data** | You will be unable to access the latest data for this user's account until the issue is resolved. | [Full Error List](https://developer.mastercard.com/open-finance-au/documentation/errors/error-list/index.md#institution-errors) ## 580 {#580} | Title | Details | |---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | **Error Code** | 580 | | **Remediation Category** | Retry Later | | **HTTP Status** | 500 | | **Data Connect Alert** | No associated alert. | | **Error Message** | Temporary connection issue for the financial institution. Wait a few minutes and try again. Submit a support ticket if the issue persists. | | **Common Causes** | This error usually happens when the bank updates its website or server. These changes can disrupt the connection between your app and the bank, requiring changes/updates to restore the original connection. | | **Troubleshooting Steps** | Submit a [support ticket](https://developer.mastercard.com/open-finance-au/documentation/support/index.md#create-a-support-case-in-scm) for troubleshooting. Simultaneously, Data Connect display alerts will automatically prompt the end user when they are in session to take suggested remediation action associated with this error. Best Practice: Developers may prompt the end users to log into their application to ensure the end users can take recommended action to resolve the issue. | | **Retriable by End User** | Yes, the end user will need to make 3-5 authentication attempts which will assist in the troubleshooting process. | | **Access to Latest Data** | You will be unable to access the latest data for this user's account until the end user resolves the issue. | [Back to top](https://developer.mastercard.com/open-finance-au/documentation/errors/institutionerrors/connection-interrupt/existing-connection-interruptions/index.md#101) [Full Error List](https://developer.mastercard.com/open-finance-au/documentation/errors/error-list/index.md)