A list of errors and warnings to help you troubleshoot your CSV imports using the (new) CSV Import API.
Analyzing the errors and warnings you encounter during the CSV import process helps you fix issues you’re facing with your CSV Imports.
Here is a list of errors that you might encounter based on different stages of the CSV import process using the (New) CSV Import API:
Message | Code | Description |
---|---|---|
invalid UTF8 format | 400 | The text encoding used in the CSV file is incorrect. |
invalid separator selected | 400 | The cell separator provided for the CSV file is incorrect. |
Missing form file | 400 | The file path is not included in the request. |
Message | Code | Description |
---|---|---|
Resource could not be found | 404 | The importId entered is incorrect, or the record has been deleted. |
Message | Code | Description |
---|---|---|
Resource could not be found | 404 | The importId entered is incorrect, or the record has been deleted. |
Parameter 'mapping_values' is invalid | 400 | An error has occurred due to one of the following reasons:
|
Parameter 'body' is invalid | 400 | The parameter value entered is not an accepted value. For example, “delta”: “On” , whereas the accepted values are true and false |
Although the import process can encounter several errors, in most cases, it usually doesn’t stop altogether. If an error occurs, the import process skips the property that caused the error and moves on to the next line or user in the CSV file. Such errors are recorded and included in the CSV import errors. They are not visible in the HTTP error code of the import request but can be viewed in the report email if a recipient’s email address has been entered during configuration. You can also identify the property or user where the error occurred by checking the import details, which can be accessed by sending a GET
request to the endpoint /users/imports/{importId}
.
The following cases will lead to warnings. However, the faulty CSV rows will be skipped, and the import will continue.
Code | Description |
---|---|
CSV_ACCESS_CODE_TOO_LONG | The given access code exceeds the maximum length. The full error message does contain the maximum allowed length. |
CSV_DUPLICATE_EXTERNAL_ID | Duplicate externalID . CSV row will be ignored. |
CSV_EMAIL_INVITE_FAILED | Unable to invite user by email. Generating a one time code instead. |
CSV_INVALID_COL_MAPPING | Invalid column mapping. For example, a profile field in the CSV file does not exist in the platform. |
CSV_INVALID_EMAIL | The user has an invalid email address. |
CSV_INVALID_EXPIRY_DATE |
|
CSV_MISSING_EXTERNAL_ID | CSV row will be skipped due to the missing identifier externalID value. |
CSV_SKIP_CURRENT_USER | CSV Import will skip current user. This can happen for deactivation or deletion. |
CSV_SKIP_USERS_WITHOUT _EXTERNAL_ID | The user will be ignored due to the missing identifier externalID . |
CSV_UNABLE_TO_ASSIGN_ACCESS _CODE_DUPLICATE | Unable to assign access code to the user because it’s already assigned to another user. |
CSV_UNABLE_TO_ASSIGN _EMAIL_CONFLICT | Unable to assign an email to the user as it’s already assigned to another user in the organization. |
CSV_UNABLE_TO_ASSIGN _EMAIL_DUPLICATE | Unable to assign an email to the user as it’s already assigned to another user. |
CSV_UNABLE_TO_CHANGE _PRIMARY_EMAIL | Unable to assign an email to the user because the user’s current primary email address was not set by an admin. |
CSV_UNABLE_TO_CREATE_USER | Unable to create a specific user. The full error message contains the cause. |
CSV_UNABLE_TO_DELETE_USER | Unable to delete a specific user. The full error message contains the cause. |
CSV_UNABLE_TO_UPDATE_USER | Unable to invite, update, or deactivate a specific user. The full error message contains the cause. |
CSV_UPLOAD_USERNAME _CONFLICT | Unable to assign a username to a user because it’s already assigned to another user in your organization. |
CSV_UPLOAD_USERNAME _DUPLICATE | Unable to assign a username to the user as it’s already used in this import file. |