What should I do if my import process fails halfway?

Imports may fail halfway due to issues such as incorrect mapping, problematic fields in the source file, incompatible file structure, or filters blocking all products. If your import stops midway:

• Check your field mapping, especially sensitive fields like Description, as incorrect mapping can cause interruptions.

• Review filters to ensure they don’t exclude all products.

• Verify that the source file format and structure match what the feed expects.

• If the issue persists after these checks, contact support so the technical team can inspect and fix backend or file‑specific issues.

In many cases, adjusting the mapping or backend settings resolves the issue and allows the import to complete successfully.

Additional known causes:

• A malformed or overly long Description field may interrupt processing.

• Nested array structures (for example in image fields) may require updated mapping syntax to parse correctly.

Additional example:

If you encounter the message “0 imported but fails halfway” and your feed contains nested image arrays, you may need to adjust the image field mapping. For example, replacing a simple path like Resimler/Resim with a JMESPath expression such as {{ data | jmespath: '["Resimler"."Resim"][]' | json }} can resolve parsing issues.

Updated on: 23/06/2026