Fixing feed errors

When a run fails, the log tells you why. Most errors fall into three buckets — the source couldn't be read, the data couldn't be processed, or the feed couldn't be delivered — and each has a clear fix.

Source / connection errors

These mean Trajekt couldn't read your catalogue. Usual causes: an expired or mistyped API token, a store URL entered wrongly (use your .myshopify.com domain for Shopify), or a security plugin blocking the API. Re-check the credential and that the source URL loads.

Processing errors

These happen while building the feed — often a rule referencing a field that doesn't exist, or a source file in an unexpected format. The log names the field or rule; adjust it and re-run.

Delivery errors

The feed built but couldn't be published — typically an SFTP credential or host problem. Confirm the SFTP details the channel gave you are entered exactly.

Still stuck?

Note the exact error text from the log and get in touch — it usually points straight to the cause.