Top Import Issues and Solutions

This article provides the list of top 10 import errors that might occur, the reason for the error and the solution for the error. For tips on importing, refer to the article on Tips on Importing on Engagement.

Import ErrorError ExplanationHow to Fix the Error
Could not run file import: Timed out

or

Could not run file import: Error reading “SSH protocol banner[Errno 104] Connection reset by peer”

Or

Error: ('Connection aborted.', OSError("(104, 'ECONNRESET')"))
The connection was closed by another part. This is most likely because the server is overloaded, so you should check the health of your SFTP server and make sure your server can handle the number of open connections and requests it is currently facing.Import connection was aborted from the source side, check connectivity and logs of your source URL.
Field 'ids': Unable to import row: No valid customer id, at least one is required and it should not be longer than 256 bytes. A valid customer id must contain at least one alphanumeric symbol and ids "null" and "undefined" are not allowed. : 3xData is missing in the import file. Verify whether all 255 lines have some value in the Ids column, so that each line can be assigned to some customers.Check the import file data
Field timestamp: This field is requiredData is missing in the import file. The import file contains an empty property timestamp.Check the import file data
Could not get sample from selected file: 1xSFTP connection error means that the server on the client's side dropped the connection for some reason.Review your server settings
Field code: voucher code with this code has been already imported to another poolImporting voucher codes are not unique or import file include empty rowsCheck if your vouchers unique and if you don't have empty rows at the end of the list
Invalid encoding in rowThe errors mean there is an encoding error inside your file/data that you are trying to upload.Review the data type and format of the data you are using to upload. The answer/fix is inside the data which at the moment could not be processed.
Error while saving schema definition for a fixed schema import: 1xIssue happens when the system tries to create catalog and import items at the same time. The only workaround, for now, is to try the same import a second time, then the catalog should be already created through the first import, so you can pick it in the UI and then it should work.Try to re-import the catalog
Field stock_level: Field is not a valid numberThe data type in the import setup is incorrectDelete this catalog, create a new one with the same name, and repeat the import. Unfortunately, you cannot change the data type of the column once it is set.

👍

Did this article help you?

Please provide your feedback. We would like to know if our help center is effective in solving your queries. You can also leave comments and suggestions on how we can make our help articles better. You can also suggest topics you’d like us to cover.