Reading the run log

Every run produces a log. Learning to read it means you catch problems before a channel does — a sudden drop in product count, a validation warning, or a delivery failure.

What the log shows

• Products read — how many came from your source.
• Products converted — how many made it into the final feed after rules and filters.
• Warnings — products with issues that were still included (e.g. missing recommended field).
• Errors — anything that stopped a product, or the whole run, from completing.
• Delivery — confirmation the feed was published or pushed by SFTP.

The number to watch

The gap between read and converted is your filters at work. A small gap is expected; a large, unexpected drop usually means a filter is too aggressive or a field isn't being read as you assumed. See products dropping out.

If a run fails

The log names the failure — a bad credential, an unreachable source, a delivery problem. Fix the named cause and re-run. You'll also get a notification if you've enabled feed alerts.