What should I do if I encounter an incorrect row separator in my feed?

This error usually happens when the structure of the feed file changes or a specific row becomes corrupted. First, download and review the latest version of the file to check for formatting problems, such as broken rows or misplaced line breaks. If the file appears normal, the separator used in the file may have changed without notice. In these cases, the row separator often needs to be manually adjusted on our backend.

Contact support with the feed name and a copy or link to the file so we can fix the row separator and ensure the feed processes correctly again.

In some cases, incorrect row separators are triggered by unexpected characters inside the file, such as stray spaces in fields (for example, an unintended space in a Description column) or encoding changes applied by the source system. Removing the problematic characters or correcting the file encoding usually resolves the issue once the backend row separator is updated.

In some cases, the issue may also be caused by intermittent file retrieval problems, encoding changes made by the supplier, or mismatched file paths (such as incorrect capitalization). Since the row separator can only be adjusted on our backend, contacting support is required whenever the file structure or encoding shifts unexpectedly.

Additional notes:

• A semicolon-delimited CSV may trigger this error if the delimiter changes or if the file includes stray characters. The delimiter must also be updated on the backend.
• A single corrupted row or an empty trailing line can cause the parser to misread the separator.
• If the feed works when uploaded manually but fails through URL/FTP, the source file may differ or contain unexpected encoding or formatting changes.

Row separator errors can also appear when a row is unintentionally split into two (for example, a Description field spilling onto the next line) or when the source file is not actually providing a valid downloadable CSV. An empty line at the end of the file does not normally trigger this error. Support will verify the source file, correct the separator on the backend, and confirm whether the issue originated from a corrupted row or an invalid source URL.

Updated on: 13/07/2026