> ## Documentation Index
> Fetch the complete documentation index at: https://docs.argyle.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Account connection errors

> Learn about errors that may occur during the account connection flow.

<Note>
  This page provides common causes and troubleshooting suggestions for account connection errors. Error codes are returned as part of the [accounts object](/legacy/api-reference/accounts#account-object) when a connection error occurs:
</Note>

* [`accounts.connection.status`](/legacy/api-reference/accounts#object-status) returns error
* [`accounts.connection.error_code`](/legacy/api-reference/accounts#object-error_code) shows the error code
* [`accounts.connection.error_message`](/legacy/api-reference/accounts#object-error_message) will provide additional information about the error

<Note>
  Some error messages shown to the user have placeholders for `[Link item name]` and `[Company name]`. In such cases, for the screens samples below, they were replaced by Starbox and GoodLoans, respectively.
</Note>

#### Error example in an account object:

```json theme={}
{
  "id": "ac81e2bc-2157-4535-8ca4-fb1f068df1fc",
  ...
  "connection": {
    "status": "error",
    "error_code": "account_disabled",
    "error_message": "This user's employment account appears to be suspended or disabled.",
    "updated_at": "2019-11-29T08:37:42.112859"
  }
  ...
}
```

## `account_disabled`

<Note>
  This error triggers the [`accounts.failed`](/legacy/api-reference/accounts-webhooks#failed) webhook.
</Note>

<Tabs>
  <Tab title="API message">
    This user's employment account appears to be suspended or disabled.
  </Tab>

  <Tab title="User message">
    Your employment account appears to be disabled. Please make sure your account is active in the `[Link item name]` system and try again.
  </Tab>

  <Tab title="Common causes">
    There are various reasons a platform may disable or suspend an employment account (e.g. violation of Terms of Service, account inactivity).
  </Tab>

  <Tab title="Troubleshooting">
    Advise the user to contact their payroll provider for further clarification.
  </Tab>
</Tabs>

![The account\_disabled account connection error screen.](https://res.cloudinary.com/argyle-media/image/upload/f_webp/v1/docs-v2/account-errors-account-disabled)

#### Account object:

```json theme={}
{
  ...
  "connection": {
    "status": "error",
    "error_code": "account_disabled",
    "error_message": "This user's employment account appears to be suspended or disabled.",
    "updated_at": "2019-11-29T08:37:42.164Z"
  }
  ...
}
```

## `account_inaccessible`

<Note>
  This error triggers the [`accounts.failed`](/legacy/api-reference/accounts-webhooks#failed) webhook.
</Note>

<Tabs>
  <Tab title="API message">
    This user's account is not currently accessible. Our team has been notified and is investigating.
  </Tab>

  <Tab title="User message">
    Your employment account could not be connected. Please make sure your account is active, you've accepted `[Link item name]` terms of service, and your onboarding is complete.
  </Tab>

  <Tab title="Common causes">
    Something unexpected happened. Argyle is investigating.
  </Tab>

  <Tab title="Troubleshooting">
    No action needed. Someone from Argyle is checking what happened. Please contact our support team for more details.
  </Tab>
</Tabs>

![The account\_inaccessible account connection error screen.](https://res.cloudinary.com/argyle-media/image/upload/f_webp/v1/docs-v2/account-errors-login-failed)

#### Account object:

```json theme={}
{
  ...
  "connection": {
    "status": "error",
    "error_code": "account_inaccessible",
    "error_message": "This user's account is not currently accessible. Our team has been notified and is investigating.",
    "updated_at": "2019-11-29T08:37:42.164Z"
  }
  ...
}
```

## `account_incomplete`

<Note>
  This error triggers the [`accounts.failed`](/legacy/api-reference/accounts-webhooks#failed) webhook.
</Note>

<Tabs>
  <Tab title="API message">
    This user's employment account is not yet active.
  </Tab>

  <Tab title="User message">
    Your employment account is not active yet. Please log in to `[Link item name]` and finish the onboarding process in order to access your account.
  </Tab>

  <Tab title="Common causes">
    The user's employment account has not been set up yet.
  </Tab>

  <Tab title="Troubleshooting">
    * Advise the user to complete the onboarding process in their payroll system.
    * Advise the user to contact their payroll provider for further support.
  </Tab>
</Tabs>

![The account\_incomplete account connection error screen.](https://res.cloudinary.com/argyle-media/image/upload/f_webp/v1/docs-v2/account-errors-account-inactive)

#### Account object:

```json theme={}
{
  ...
  "connection": {
    "status": "error",
    "error_code": "account_incomplete",
    "error_message": "This user's employment account is not yet active.",
    "updated_at": "2019-11-29T08:37:42.164Z"
  }
  ...
}
```

## `auth_required`

<Tabs>
  <Tab title="API message">
    This user's connection has expired and requires re-authentication.
  </Tab>

  <Tab title="User message">
    Please reconnect your `[Link item name]` account to continue sharing data with `[Company name]`.
  </Tab>

  <Tab title="Common causes">
    The platform has disconnected a previously connected account. Some platforms have short-living sessions and require users to re-authenticate more often.
  </Tab>

  <Tab title="Troubleshooting">
    Advise the user to reconnect.
  </Tab>
</Tabs>

![The auth\_required account connection error screen.](https://res.cloudinary.com/argyle-media/image/upload/v1658498351/docs-readme/account-auth_required-error.png)

#### Account object:

```json theme={}
{
  ...
  "connection": {
    "status": "error",
    "error_code": "auth_required",
    "error_message": "This user's connection has expired and requires re-authentication.",
    "updated_at": "2019-11-29T08:37:42.164Z"
  }
  ...
}
```

## `expired_credentials`

<Note>
  This error triggers the [`accounts.failed`](/legacy/api-reference/accounts-webhooks#failed) webhook.
</Note>

<Tabs>
  <Tab title="API message">
    This user provided credentials which are out of date so a password reset is required.
  </Tab>

  <Tab title="User message">
    Your login credentials have expired. Please reset the password for your `[Link item name]` account and try again.
  </Tab>

  <Tab title="Common causes">
    Sometimes a platform may alert the user that someone has tried to connect their employment account and the user changes their password.
  </Tab>

  <Tab title="Troubleshooting">
    * Advise the user to use their newest password.
    * Ask the user if they are able to log in directly to the platform's website or app.
    * Advise the user to change their password and then try to connect their account again.
  </Tab>
</Tabs>

![The expired\_credentials account connection error screen.](https://res.cloudinary.com/argyle-media/image/upload/v1661344432/docs-v2/20220824_account_connection_errors_1.jpg)

#### Account object:

```json theme={}
{
  ...
  "connection": {
    "status": "error",
    "error_code": "expired_credentials",
    "error_message": "This user provided credentials which are out of date (i.e., a password reset is required).",
    "updated_at": "2019-11-29T08:37:42.164Z"
  }
  ...
}
```

## `invalid_account_type`

<Note>
  This error triggers the [`accounts.failed`](/legacy/api-reference/accounts-webhooks#failed) webhook.
</Note>

<Tabs>
  <Tab title="API message">
    This user provided credentials for the wrong account type (e.g., a passenger account rather than a driver account, or an admin account rather than an employee account).
  </Tab>

  <Tab title="User message">
    This is an unsupported account type (e.g. a rider account instead of a driver account). Please log in with credentials for your employment-related account with `[Link item name]`.
  </Tab>

  <Tab title="Common causes">
    Sometimes users try to enter credentials of platforms they use as a service instead of using their payroll system credentials.
  </Tab>

  <Tab title="Troubleshooting">
    * Confirm if the user is able to log in directly to the platform's website or app.
    * Confirm if the user is using their payroll system credentials and not credentials of a platform they use as a service.
  </Tab>
</Tabs>

![The invalid\_account\_type account connection error screen.](https://res.cloudinary.com/argyle-media/image/upload/f_webp/v1/docs-v2/account-errors-invalid_account_type)

#### Account object:

```json theme={}
{
  ...
  "connection": {
    "status": "error",
    "error_code": "invalid_account_type",
    "error_message": "This user provided credentials for the wrong account type (e.g., a passenger account rather than a driver account, or an admin account rather than an employee account).",
    "updated_at": "2019-11-29T08:37:42.164Z"
  }
  ...
}
```

## `invalid_auth`

<Note>
  This error triggers the [`accounts.failed`](/legacy/api-reference/accounts-webhooks#failed) webhook.
</Note>

<Tabs>
  <Tab title="API message">
    This user's account connection was unsuccessful due to invalid credentials or due to failed or misconfigured multi-factor authentication (MFA).
  </Tab>

  <Tab title="User message">
    Your connection was unsuccessful due to invalid credentials or due to failed or misconfigured multi-factor authentication (MFA).
  </Tab>

  <Tab title="Common causes">
    Some platforms do not provide visibility whether the connection failed due to invalid credentials or invalid multi-factor authentication (MFA).
  </Tab>

  <Tab title="Troubleshooting">
    * Check if the user is able to log in directly to the platform's website or app.
    * Confirm the user is using their correct login credentials.
    * Check if the user has received an MFA request.
    * Confirm the user is using the correct MFA device.
  </Tab>
</Tabs>

![The invalid\_auth account connection error screen.](https://res.cloudinary.com/argyle-media/image/upload/v1663000120/docs-2022/Guides/Troubleshooting/Account%20connection%20errors/invalid-auth-error.png)

#### Account object:

```json theme={}
{
  ...
  "connection": {
    "status": "error",
    "error_code": "invalid_auth",
    "error_message": "This user's account connection was unsuccessful due to invalid credentials or due to failed or misconfigured multi-factor authentication (MFA).",
    "updated_at": "2019-11-29T08:37:42.164Z"
  }
  ...
}
```

## `invalid_credentials`

<Note>
  This error triggers the [`accounts.failed`](/legacy/api-reference/accounts-webhooks#failed) webhook.
</Note>

<Tabs>
  <Tab title="API message">
    This user provided invalid credentials.
  </Tab>

  <Tab title="User message">
    Invalid credentials. Please try again.
  </Tab>

  <Tab title="Common causes">
    Sometimes a user may enter their credentials of a platform they use as a service instead of their payroll system credentials.
  </Tab>

  <Tab title="Troubleshooting">
    * Confirm if the user is able to log in directly to the platform's website or app.
    * Confirm if the user is using their payroll system credentials and not credentials of a platform they use as a service.
    * Advise the user to attempt connecting their account again.
    * Advise the user to change their password and then try to connect their account again.
  </Tab>
</Tabs>

![The invalid\_credentials account connection error screen.](https://res.cloudinary.com/argyle-media/image/upload/v1661344437/docs-v2/20220824_account_connection_errors_2.jpg)

#### Account object:

```json theme={}
{
  ...
  "connection": {
    "status": "error",
    "error_code": "invalid_credentials",
    "error_message": "This user provided invalid credentials.",
    "updated_at": "2019-11-29T08:37:42.164Z"
  }
  ...
}
```

## `invalid_login_method`

<Note>
  This error triggers the [`accounts.failed`](/legacy/api-reference/accounts-webhooks#failed) webhook.
</Note>

<Tabs>
  <Tab title="API message">
    This user tried to log in using an authentication method that is not supported by employer.
  </Tab>

  <Tab title="User message">
    Your Company ID cannot be used with selected login method. Please use a different login method.
  </Tab>

  <Tab title="Common causes">
    This platform currently supports login methods that are different than the one attempted by the user when trying to connect.
  </Tab>

  <Tab title="Troubleshooting">
    Advise the user to select different available login method. For example, some specific employers might only support default login methods and the others only support SSO.
  </Tab>
</Tabs>

![The invalid\_login\_method account connection error screen.](https://res.cloudinary.com/argyle-media/image/upload/v1669660210/docs-2022/Guides/Troubleshooting/Account%20connection%20errors/invalid_login_method.png)

#### Account object:

```json theme={}
{
  ...
  "connection": {
    "status": "error",
    "error_code": "invalid_login_method",
    "error_message": "This user tried to log in using an authentication method that is not supported by employer.",
    "updated_at": "2022-11-27T04:12:42.154Z"
  }
  ...
}
```

## `invalid_mfa`

<Tabs>
  <Tab title="API message">
    This user did not provide the correct multi-factor authentication response.
  </Tab>

  <Tab title="User message">
    Multi-factor authentication was not successful. Please try again.
  </Tab>

  <Tab title="Common causes">
    This user did not provide the correct multi-factor authentication (MFA) response that was requested by the platform (e.g. SMS code, click on the link in email, etc).
  </Tab>

  <Tab title="Troubleshooting">
    * Confirm if the user is able to log in directly to the platform's website or app.
    * Check with the user if they have received the MFA request.
    * Confirm the user is using the correct MFA device.
  </Tab>
</Tabs>

![The invalid\_mfa account connection error screen.](https://res.cloudinary.com/argyle-media/image/upload/f_webp/v1/docs-v2/account-errors-invalid_mfa)

#### Account object:

```json theme={}
{
  ...
  "connection": {
    "status": "error",
    "error_code": "invalid_mfa",
    "error_message": "This user did not provide the correct multi-factor authentication response.",
    "updated_at": "2019-11-29T08:37:42.164Z"
  }
  ...
}
```

## `login_attempts_exceeded`

<Note>
  This error triggers the [`accounts.failed`](/legacy/api-reference/accounts-webhooks#failed) webhook.
</Note>

<Tabs>
  <Tab title="API message">
    This user provided invalid credentials too many times, causing them to be temporarily unable to attempt further logins.
  </Tab>

  <Tab title="User message">
    Unavailable because of too many failed login attempts. Please try again in a few hours.
  </Tab>

  <Tab title="Common causes">
    The platform temporarily disabled login attempts for this employment account due to entering invalid credentials too many times.
  </Tab>

  <Tab title="Troubleshooting">
    * Advise the user to wait a few hours before attempting to connect their account again.
    * Confirm if the user is able to log in directly to the platform's website or app.
  </Tab>
</Tabs>

![The login\_attempts\_exceeded account connection error screen.](https://res.cloudinary.com/argyle-media/image/upload/f_webp/v1/docs-v2/account-errors-login_attempts_exceeded)

#### Account object:

```json theme={}
{
  ...
  "connection": {
    "status": "error",
    "error_code": "login_attempts_exceeded",
    "error_message": "This user provided invalid credentials too many times, causing them to be temporarily unable to attempt further logins.",
    "updated_at": "2019-11-29T08:37:42.164Z"
  }
  ...
}
```

## `mfa_attempts_exceeded`

<Note>
  This error triggers the [`accounts.failed`](/legacy/api-reference/accounts-webhooks#failed) webhook.
</Note>

<Tabs>
  <Tab title="API message">
    This user failed multi-factor authentication too many times, causing them to be unable to attempt further logins until multi-factor authentication method is reset.
  </Tab>

  <Tab title="User message">
    Unavailable because of too many unsuccessful multi-factor authentication attempts. Please log in to `[Link item name]` and reset your multi-factor authentication method.
  </Tab>

  <Tab title="Common causes">
    The platform permanently disabled login attempts for this employment account due to entering an invalid MFA too many times. It only can be resolved by the user resetting MFA directly on the payroll system.
  </Tab>

  <Tab title="Troubleshooting">
    * Check if the user is able to log in directly via the platform's website or app.
    * Advise the user to reset their MFA method on the platform's website or app.
    * Advise the user to attempt the account connection again using the new MFA.
  </Tab>
</Tabs>

![The mfa\_attempts\_exceeded account connection error screen.](https://res.cloudinary.com/argyle-media/image/upload/f_webp/v1/docs-v2/c-019_mfa_attempts_exceeded_error)

#### Account object:

```json theme={}
{
  ...
  "connection": {
    "status": "error",
    "error_code": "mfa_attempts_exceeded",
    "error_message": "This user failed multi-factor authentication too many times, causing them to be unable to attempt further logins until multi-factor authentication method is reset.",
    "updated_at": "2019-11-29T08:37:42.164Z"
  }
  ...
}
```

## `mfa_exhausted`

<Note>
  This error triggers the [`accounts.failed`](/legacy/api-reference/accounts-webhooks#failed) webhook.
</Note>

<Tabs>
  <Tab title="API message">
    This user failed multi-factor authentication too many times, requiring them to re-authenticate.
  </Tab>

  <Tab title="User message">
    Unavailable because of too many failed multi-factor authentication attempts. `[Link item name]` requires you to log in again.
  </Tab>

  <Tab title="Common causes">
    The platform requires a full re-authentication for this employment account due to entering invalid MFA too many times.
  </Tab>

  <Tab title="Troubleshooting">
    Advise the user to attempt account connection again.
  </Tab>
</Tabs>

![The mfa\_exhausted account connection error screen.](https://res.cloudinary.com/argyle-media/image/upload/f_webp/v1/docs-v2/account-errors-mfa_exhausted)

#### Account object:

```json theme={}
{
  ...
  "connection": {
    "status": "error",
    "error_code": "mfa_exhausted",
    "error_message": "This user failed multi-factor authentication too many times, requiring them to re-authenticate.",
    "updated_at": "2019-11-29T08:37:42.164Z"
  }
  ...
}
```

## `mfa_not_configured`

<Note>
  This error triggers the [`accounts.failed`](/legacy/api-reference/accounts-webhooks#failed) webhook.
</Note>

<Tabs>
  <Tab title="API message">
    This user has not configured multi-factor authentication for their employment account, restricting access to the user's employment data.
  </Tab>

  <Tab title="User message">
    Please log in to `[Link item name]` and configure multi-factor authentication to continue sharing your data with `[Company name]`.
  </Tab>

  <Tab title="Common causes">
    The platform does not allow to access the employment data of this account as it does not have a mandatory multi-factor authentication set up.
  </Tab>

  <Tab title="Troubleshooting">
    Advise the user to configure a multi-factor authentication method on their payroll system and attempt account connection again.
  </Tab>
</Tabs>

![The mfa\_not\_configured account connection error screen.](https://res.cloudinary.com/argyle-media/image/upload/f_webp/v1/docs-v2/account-errors-mfa_not_configured)

#### Account object:

```json theme={}
{
  ...
  "connection": {
    "status": "error",
    "error_code": "mfa_not_configured",
    "error_message": "This user has not configured multi-factor authentication for their employment account, restricting access to the user's employment data.",
    "updated_at": "2019-11-29T08:37:42.164Z"
  }
  ...
}
```

## `mfa_timeout`

<Note>
  This error triggers the [`accounts.failed`](/legacy/api-reference/accounts-webhooks#failed) webhook.
</Note>

<Tabs>
  <Tab title="API message">
    This user did not complete multi-factor authentication.
  </Tab>

  <Tab title="User message">
    Your multi-factor authentication (MFA) session has expired. Please log in again to complete the MFA process.
  </Tab>

  <Tab title="Common causes">
    The user did not submit the requested MFA response necessary to connect an account within the given time period.
  </Tab>

  <Tab title="Troubleshooting">
    * Confirm the user has received the MFA request.
    * Have the user check if the information for their MFA device or phone number is correct.
    * Have the user confirm they are able to log in directly via the platform's website or app.
    * In the case of an SMS or Voice MFA, advise the user to make sure they are able to receive messages from the platform.
    * If there is an issue, contact the platform's support.
    * Advise the user to attempt the account connection again.
  </Tab>
</Tabs>

![The mfa\_timeout account connection error screen.](https://res.cloudinary.com/argyle-media/image/upload/f_webp/v1/docs-v2/account-errors-mfa_timeout)

#### Account object:

```json theme={}
{
  ...
  "connection": {
    "status": "error",
    "error_code": "mfa_timeout",
    "error_message": "This user did not complete multi-factor authentication.",
    "updated_at": "2019-11-29T08:37:42.164Z"
  }
  ...
}
```

## `physical_mfa_unsupported`

<Note>
  This error triggers the [`accounts.failed`](/legacy/api-reference/accounts-webhooks#failed) webhook.
</Note>

<Tabs>
  <Tab title="API message">
    This user's employment account uses a physical multi-factor authentication method that Argyle does not currently support.
  </Tab>

  <Tab title="User message">
    Please log in to `[Link item name]` system and disable the physical multi-factor authentication method (e.g. USB). Then set up another multi-factor authentication method and try again.
  </Tab>

  <Tab title="Common causes">
    The user attempted to use a physical multi-factor authentication method that Argyle does not support.
  </Tab>

  <Tab title="Troubleshooting">
    The user should disable the physical multi-factor authentication method, then set up an alternative multi-factor authentication method and try again.
  </Tab>
</Tabs>

![The physical\_mfa\_unsupported account connection error screen.](https://res.cloudinary.com/argyle-media/image/upload/f_webp/v1/docs-v2/physical_mfa_unsupported)

#### Account object:

```json theme={}
{
  ...
  "connection": {
    "status": "error",
    "error_code": "physical_mfa_unsupported",
    "error_message": "This user's employment account uses a physical multi-factor authentication method that Argyle does not currently support.",
    "updated_at": "2019-11-29T08:37:42.164Z"
  }
  ...
}
```

## `service_unavailable`

<Note>
  This error triggers the [`accounts.failed`](/legacy/api-reference/accounts-webhooks#failed) webhook.
</Note>

<Tabs>
  <Tab title="API message">
    The platform this user is attempting to connect to is currently unavailable. See the Coverage page in Argyle Console for additional information.
  </Tab>

  <Tab title="User message">
    `[Link item name]` system is currently unavailable. Please try again later.
  </Tab>

  <Tab title="Common causes">
    The platform may be fully or partially unavailable if it is experiencing downtime. This could be planned maintenance or an unexpected service degradation causing the account connection failure. See [Coverage](https://console.argyle.com/coverage) in Argyle Console for additional information.
  </Tab>

  <Tab title="Troubleshooting">
    * Have the user to check if they are able to log in directly to the platform's website or app.
    * Advise the user to try connecting their account again.
  </Tab>
</Tabs>

![The service\_unavailable account connection error screen.](https://res.cloudinary.com/argyle-media/image/upload/f_webp/v1/docs-v2/account-errors-service_unavailable)

#### Account object:

```json theme={}
{
  ...
  "connection": {
    "status": "error",
    "error_code": "service_unavailable",
    "error_message": "The platform this user is attempting to connect to is currently unavailable. See the Coverage page in Argyle Console for additional information.",
    "updated_at": "2019-11-29T08:37:42.164Z"
  }
  ...
}
```

## `system_error`

<Note>
  This error triggers the [`accounts.failed`](/legacy/api-reference/accounts-webhooks#failed) webhook.
</Note>

<Tabs>
  <Tab title="API message">
    Argyle encountered a problem connecting to this account. Our team has been notified and is investigating.
  </Tab>

  <Tab title="User message">
    We've encountered an unexpected error. Please try again later.
  </Tab>

  <Tab title="Common causes">
    Something unexpected happened (i.e. service unavailable, invalidated session, etc).
  </Tab>

  <Tab title="Troubleshooting">
    No action needed. Someone from Argyle is checking what happened. Please contact our support team for more details.
  </Tab>
</Tabs>

![The system\_error account connection error screen.](https://res.cloudinary.com/argyle-media/image/upload/f_webp/v1/docs-v2/account-errors-system_error)

#### Account object:

```json theme={}
{
  ...
  "connection": {
    "status": "error",
    "error_code": "system_error",
    "error_message": "Argyle encountered a problem connecting to this account. Our team has been notified and is investigating.",
    "updated_at": "2019-11-29T08:37:42.164Z"
  }
  ...
}
```

## `tos_required`

<Note>
  This error triggers the [`accounts.failed`](/legacy/api-reference/accounts-webhooks#failed) webhook.
</Note>

<Tabs>
  <Tab title="API message">
    This user has not accepted the Terms of Service presented by their payroll provider, preventing access to their employment account.
  </Tab>

  <Tab title="User message">
    Please log in to `[Link item name]` and make sure you've accepted the latest terms and conditions to continue sharing your data with `[Company name]`. Click try again to reactivate your connection.
  </Tab>

  <Tab title="Common causes">
    The payroll system requires the user to accept the Terms of Service to allow access to the employment account.
  </Tab>

  <Tab title="Troubleshooting">
    * Advise the user to log in to their payroll system to accept the latest Terms of Service and then try connecting an account again.
    * Advise the user to contact their payroll provider for further clarification.
  </Tab>
</Tabs>

![The tos\_required account connection error screen.](https://res.cloudinary.com/argyle-media/image/upload/f_webp/v1/docs-v2/account-errors-tos_required)

#### Account object:

```json theme={}
{
  ...
  "connection": {
    "status": "error",
    "error_code": "tos_required",
    "error_message": "This user has not accepted the Terms of Service presented by their payroll provider, preventing access to their employment account.",
    "updated_at": "2019-11-29T08:37:42.164Z"
  }
  ...
}
```

## `trial_connections_exhausted`

<Tabs>
  <Tab title="API message">
    This account could not be connected because you've reached your limit for free account connections in trial mode. Reach out to Argyle or visit Argyle Console to enable full access and connect unlimited accounts.
  </Tab>

  <Tab title="User message">
    Connection is currently unavailable. Please reach out to `[Link item name]` for help.
  </Tab>

  <Tab title="Common causes">
    This account could not be connected because you've reached your limit for free account connections in trial mode.
  </Tab>

  <Tab title="Troubleshooting">
    Contact Argyle or visit Argyle Console to enable full access and connect unlimited accounts.
  </Tab>
</Tabs>

![The trial\_connections\_exhausted account connection error screen.](https://res.cloudinary.com/argyle-media/image/upload/f_webp/v1/docs-v2/account-errors-PayDistributionStatus.ServiceUnavailable)

#### Account object:

```json theme={}
{
  ...
  "connection": {
    "status": "error",
    "error_code": "trial_connections_exhausted",
    "error_message": "This account could not be connected because you've reached your limit for free account connections in trial mode. Reach out to Argyle or visit Argyle Console to enable full access and connect unlimited accounts.",
    "updated_at": "2020-12-29T08:37:42.164Z"
  }
  ...
}
```

## `trial_period_expired`

<Note>
  This error triggers the [`accounts.failed`](/legacy/api-reference/accounts-webhooks#failed) webhook.
</Note>

<Tabs>
  <Tab title="API message">
    This user's employment account is in a trial account, and is currently disabled because the trial period has expired.
  </Tab>

  <Tab title="User message">
    Your employment account is a trial account that has expired. Please log in to `[Link item name]` system to reactivate your account and try again.
  </Tab>

  <Tab title="Common causes">
    This user's employment account was a trial account and is currently disabled because the trial period has expired.
  </Tab>

  <Tab title="Troubleshooting">
    Advise the user to contact their payroll provider for further clarification.
  </Tab>
</Tabs>

![The trial\_period\_expired account connection error screen.](https://res.cloudinary.com/argyle-media/image/upload/f_webp/v1/docs-v2/account-errors-trial_expired)

#### Account object:

```json theme={}
{
  ...
  "connection": {
    "status": "error",
    "error_code": "trial_period_expired",
    "error_message": "This user's employment account is in a trial account, and is currently disabled because the trial period has expired.",
    "updated_at": "2019-11-29T08:37:42.164Z"
  }
  ...
}
```

## `unsupported_auth_type`

<Note>
  This error triggers the [`accounts.failed`](/legacy/api-reference/accounts-webhooks#failed) webhook.
</Note>

<Tabs>
  <Tab title="API message">
    This user tried to log in using single sign-on (e.g., Google, Facebook), which Argyle does not currently support.
  </Tab>

  <Tab title="User message">
    Single sign-on (SSO) login method is not supported. Please use a different login method.
  </Tab>

  <Tab title="Common causes">
    Argyle currently does not support single sign-on authentication methods, therefore a direct authentication method should be used.
  </Tab>

  <Tab title="Troubleshooting">
    Advise the user to instead connect their account using a direct authentication method.
  </Tab>
</Tabs>

![The unsupported\_auth\_type account connection error screen.](https://res.cloudinary.com/argyle-media/image/upload/f_webp/v1/docs-v2/account-errors-unsupported_auth_type)

#### Account object:

```json theme={}
{
  ...
  "connection": {
    "status": "error",
    "error_code": "unsupported_auth_type",
    "error_message": "This user tried to log in using single sign-on (e.g., Google, Facebook), which Argyle does not currently support.",
    "updated_at": "2019-11-29T08:37:42.164Z"
  }
  ...
}
```

## `unsupported_mfa_method`

<Note>
  This error triggers the [`accounts.failed`](/legacy/api-reference/accounts-webhooks#failed) webhook.
</Note>

<Tabs>
  <Tab title="API message">
    This user's employment account uses a multi-factor authentication method that Argyle does not currently support.
  </Tab>

  <Tab title="User message">
    We were not able to connect your employment account. Please log in to `[Link item name]` to update your multi-factor authentication method and try again.
  </Tab>

  <Tab title="Common causes">
    The user's employment account uses an MFA method currently not supported by Argyle.
  </Tab>

  <Tab title="Troubleshooting">
    Advise the user to disable or change the MFA method.
  </Tab>
</Tabs>

![The unsupported\_mfa\_method account connection error screen.](https://res.cloudinary.com/argyle-media/image/upload/f_webp/v1/docs-v2/account-errors-unsupported_mfa)

#### Account object:

```json theme={}
{
  ...
  "connection": {
    "status": "error",
    "error_code": "unsupported_mfa_method",
    "error_message": "This user's employment account uses a multi-factor authentication method that Argyle does not currently support.",
    "updated_at": "2019-11-29T08:37:42.164Z"
  }
  ...
}
```