Skip to main content

Check a channel's sync activity

When something has not reached the store, or an order has not arrived, the channel's own page under Integrations is where to look. Needs organisation-admin access.

Failed pushes​

Pushes that failed are collected per channel, each with its error, rather than left to be found variant by variant.

A push failure is not necessarily lost work: the routine sweep re-sends current stock figures, so a stock push that failed once is usually corrected without intervention. A listing that failed to publish will not fix itself the same way — the variant stays unpublished until the push succeeds.

Work through repeated failures rather than one-offs. The same variant failing every time points at something about that variant; everything failing at once points at the connection.

Recent events from the store​

A tail of what the store has sent recently. Useful for the specific question "did that order actually reach us?" — if the event is not there, the problem is between the store and Yessort rather than inside Yessort.

Changes to the connection​

A history of changes made to the connection and its settings, so a change in behaviour can be traced to the change that caused it. Worth checking when a channel starts behaving differently and nobody remembers altering anything.

Catalogue sync history​

The Catalogue sync card shows the last run and how it ended — Last sync completed with its counts, Last sync failed with a reason, or No sync has run yet.

The counts tell you what a run actually did: how much was staged, how much matched to existing variants, and how much was deferred to the review queue.

The connection's own state​

A connection is active, paused, or in error, separately from the channel's status. A connection in error keeps its last error until the next successful sync clears it.

Credentials that have stopped working are the common cause. Re-authorize replaces them without losing the channel, its links or its history.

Stock differences are elsewhere​

Differences between your stock and the store's are not push failures and are not reported here. They are found by the nightly and weekly checks in keeping stock in step.