> ## 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.

# Recovery and Errors

> Resume incomplete sessions and correct invalid verification requests.

Use the verification's current `status.state`, `status.code`, and `status.errors` to decide whether to resume the existing verification or create a new one.

## Choose a recovery action

| Status or situation                            | Action                                                                                           |
| ---------------------------------------------- | ------------------------------------------------------------------------------------------------ |
| Active verification; session closed or expired | Create another session for the same verification.                                                |
| `connection_attempted`                         | Review the account connection error and return the user to the active verification.              |
| `syncing_error`                                | Create another session so the user can complete MFA or other required action.                    |
| `more_data_required`                           | Upload the additional Doc VOI documents for the same user.                                       |
| `cancelled_by_client` or `argyle_timeout`      | The verification cannot be resumed. Create a new verification if another attempt is appropriate. |
| `system_error`                                 | Review `status.errors` and contact Argyle Support before retrying.                               |

## Session not completed

If the user closes the connection flow, or the session link expires, retrieve the verification and check its current status.

When the verification remains active in `pending` or `user_session_started`, create a new session for the same verification with [`POST /v2/sessions`](/verifications/quickstart#create-a-session). Do not create another verification solely to replace an expired session link.

For `connection_attempted` or `syncing_error`, review the current [Account Connection Error](/api-reference/account-connection-errors), correct the issue, and create another session for the same active verification.

## User details missing or invalid

If `POST /v2/verifications` returns a 400 response for missing or invalid user details:

1. Update the user with [`PATCH /v2/users/{id}`](/api-reference/users/update-a-user).
2. Retry `POST /v2/verifications`.

## More documents required

When a Doc VOI verification enters `more_data_required`, review `status.errors` for the missing information. Upload the additional files for the same user with [`POST /v2/user-uploads`](/api-reference/user-uploads/upload-a-document). Continue listening for the `verifications.updated` webhook as processing resumes.