# Connection Migration in Progress source: https://developer.mastercard.com/open-finance-au/documentation/errors/institutionerrors/connection-migration-inprogress/index.md Following error codes indicate that the selected account cannot be added. This error occurs when an account is migrated from a legacy or a non-OAuth-based connection to an OAuth connection and requires customer to provide their consent again. ## 945 {#945} | Title | Details | |---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | **Error Code** | 945 | | **Remediation Category** | Invalid Input | | **HTTP Status** | 500 | | **Data Connect Alert** | No associated alert. | | **Error Message** | The account is migrated but not consented on OAuth.​ | | **Common Causes** | This error occurs when the connection to a financial institution is in the process of migrating from legacy or non-OAuth-based connection to an OAuth connection. It may be possible that the OAuth token no longer has access to the account or the account has migrated but the user has not yet completed the OAuth consent flow. The end users need to provide their consent again using the new OAuth flow. | | **Troubleshooting Steps** | Prompt the end user to re-authenticate via ​[Data Connect Fix](https://developer.mastercard.com/open-finance-au/documentation/connect/generate-2-connect-url-apis/index.md). | | **Data Connect Fix** | [Data Connect Fix](https://developer.mastercard.com/open-finance-au/documentation/connect/generate-2-connect-url-apis/index.md) flow can be leveraged to enable your end users to re-authenticate. This is a separate integration. To know more about Data Connect Fix, contact your account management representative. ​If Data Connect Fix is already integrated, then try a refresh request. If refresh request fails to address the issue, 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** | Yes, the end user can reauthenticate if Data Connect Fix is integrated.​ | | **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) ## 948 {#948} | Title | Details | |---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | **Error Code** | 948 | | **Remediation Category** | Re-Authenticate or Provide Additional Information | | **HTTP Status** | 500 | | **Data Connect Alert** | No associated alert. | | **Error Message** | The account has been migrated to OAuth and is waiting for the customer to authenticate.​ | | **Common Causes** | This error occurs when the connection to a financial institution is in the process of migrating from legacy or non-OAuth-based connection to an OAuth connection. It may be possible that the OAuth token no longer has access to the account or the account has migrated but the user has not yet completed the OAuth consent flow. The end users need to provide their consent again using the new OAuth flow. | | **Troubleshooting Steps** | Prompt the end user to re-authenticate via ​[Data Connect Fix](https://developer.mastercard.com/open-finance-au/documentation/connect/generate-2-connect-url-apis/index.md). ​ | | **Data Connect Fix** | [Data Connect Fix](https://developer.mastercard.com/open-finance-au/documentation/connect/generate-2-connect-url-apis/index.md) flow can be leveraged to enable your end users to re-authenticate. This is a separate integration. To know more about Data Connect Fix, contact your account management representative. ​If Data Connect Fix is already integrated, then try a refresh request. If refresh request fails to address the issue, 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** | Yes, the end user can reauthenticate if Data Connect Fix is integrated.​ | | **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)