What should I do if my email feeds are not processing as expected?

If your email feed isn't processing, check these common causes and solutions:

• Hit a Variant Limit? Your feed may have reached its product limit. Apply a filter (like Vendor) to reduce the size and resume processing.
• Case-Sensitive Field Mappings? Ensure your column names match exactly. For example, if your file uses QUANTITY in all caps, it will fail if mapped to lowercase Quantity.
• Wrong Sender Email? Some feeds only accept files from approved sender addresses. Double-check that the file was sent from the correct email.
• Stuck Feed? If the email was received but hasn't been processed, manually trigger the update by using the Force Run option. It will always process the latest file received.
• Queued Due to Schedule? Email feeds only process at their scheduled run time unless your plan supports faster frequency. Even if a new email arrives, it will wait for the next scheduled run.
• Temporary System Hiccups or Maintenance? If emails are received but updates happen irregularly or skip runs, it may be due to temporary backend maintenance or processing hiccups. These typically resolve once the system stabilizes.
• Attachment Received but Not Processed? In some cases, the raw email log may show an attachment received, but the feed still displays an empty file. This can indicate a connection issue that requires a backend fix. After the fix is applied, resend the email to allow the feed to process correctly.
• Another Feed Is Processing? Only one feed can run at a time. If another feed is currently processing, email feeds will remain queued until it completes.
• Structure or Parent Node Errors? If you see formatting errors, reviewing and updating your structure/parent node mappings will usually fix them.

Updated on: 17/07/2026