Skip to main content

Channel sync statuses

Two different things carry a status: the link between one variant and one channel, and a catalogue sync run covering a whole channel.

StatusMeaning
Not pushedNever sent to the channel. Where a new link starts
PendingA push is queued and has not been acknowledged yet
SyncedThe last push succeeded. The channel's identifiers are recorded
FailedThe last push failed. The error is kept against the link

A failed link keeps its error message until the next successful push, which clears it. Failures are collected per channel so you can see them together rather than hunting variant by variant — see check a channel's sync activity.

Kinds of catalogue sync run​

KindWhat it does
SyncReads the store and reconciles what it finds into Yessort — re-discovering new products and refreshing linked ones. Nothing is discarded
ResetClears this channel's pulled catalogue staging first, then reads fresh. Destructive, and confirmed before it runs

Only one run at a time per channel. Starting a second while one is in flight is refused.

Statuses of a sync run​

StatusMeaning
PendingQueued. The store has not been asked for the export yet
ExportingThe store is building the export. Most of the wall-clock time sits here
IngestingThe export is downloaded and rows are being staged
MatchingStaged rows are compared with your catalogue and each is given a proposed decision. Quick
CompletedFinished. The counts are final
FailedStopped, with a reason

Exporting shows a count rather than a progress bar. The store reports how many objects it has exported so far, but not how many there will be in total, so there is no percentage to show. Ingesting does have both numbers, so it shows a real bar.

What a completed run reports​

How many products and variants were staged, and the outcome of matching: how many were linked to existing variants, how many are proposed as new, and how many were deferred for you to decide on. That last figure is the size of the review queue the run created.