Docs / Sync logs

Sync logs

Sync logs is the record of every run: each supplier file, each Supplier API fetch and each channel push, with the log lines it wrote. It is where you find out w

Illustration coming soon

Sync logs

Sync logs is the record of every run: each supplier file, each Supplier API fetch and each channel push, with the log lines it wrote. It is where you find out what a run did to which SKU on which channel, and why something was skipped.

What a run is

Every file and every fetch becomes one run. The list shows, for each run:

  • Run # — its number; the Dashboard and the Supplier API page link straight to a run.
  • Source — Email CSV, Upload, API (a Supplier API fetch) or Channel (a push that did not come from a feed, such as a product removal).
  • Supplier — whose numbers ran.
  • Status — the live stage while it runs (reading the file, matching SKUs, then "Syncing Shopify", "Syncing eBay", "Syncing Walmart", "Syncing Amazon", "Syncing Etsy", "Syncing WooCommerce"), then Completed, Completed with warnings or Failed.
  • What changed — how many SKUs were updated and how many rows could not be matched to your catalog.
  • Started — when it began, in your local time.
  • Reprocess on a file that is still stored, Fetch again on a Supplier API run.

Filter the list by source, by supplier, or open a single run with the link in a log line.

The log lines

Under the runs, the Logs panel lists the most recent lines across your runs, newest first, each with a badge:

  • Info — what the run did: "Feed parsed", "Syncing WooCommerce", "WooCommerce updates pushed" with the counts, "Prices not pushed to " with the reason, "Manual re-run of an earlier feed".
  • Warning — something to look at that did not stop the run: SKUs the channel does not list ("not listed", with the SKUs checked), items a channel skipped and the first error it gave, no active connection for a channel.
  • Error — a channel refused the whole batch, or the file could not be read. The message is the channel's own words.

Open a line to see its context: the SKUs it concerns, the counts, the store or connection it talked to, and the exact error text. To find a problem: filter to the supplier, open the run from the Dashboard or the Feed uploads row, read the warning and error lines for that run, and look at the context for the SKU. A "not listed" SKU is one the channel does not know under that exact SKU; a "skipped" item carries the channel's error.

Reprocess

Reprocess re-runs that saved file as if it had just arrived, as a new run at the top of the list, pointing back at the original. Its numbers become the current stock for that supplier and go to every connected channel. Use it after fixing a mapping or a connection, or to push a supplier's last known numbers again. It is the same action as Push on the file's row on Feed uploads.

What it does not do: it does not fetch anything new from the supplier (a Supplier API run has Fetch again for that), and it cannot run a file whose contents are no longer stored. Only the 20 most recent files of your account keep their contents; older runs show "Feed expired".

Compare

When a run changed a quantity on a channel, the run's row on Feed uploads and the Dashboard links to Compare, the before-and-after view of that run per channel. A run that changed nothing says so instead of linking.

Channels in a run

A run pushes to every channel its supplier is connected to, each as its own stage with its own counts: Shopify, eBay, Walmart, Amazon, Etsy and WooCommerce. A channel that fails is logged as an error and the run carries on with the others.

← Previous Feed uploads Next → Suppli Mail