Sync queue and health

Read queue behaviour and respond to health signals quickly.

Last updated:

Use Control Centre to review current per-channel health signals, including recent failures, retries, and last successful sync times.

Queue fundamentals

Each sync action enters a queue with retry metadata and event history.

  • Manual refreshes and scheduled syncs are queued so ChannelWeave can retry safely when a channel is slow or temporarily unavailable.
  • Repeated refresh clicks are coalesced so the same channel is not flooded with duplicate requests.
  • Connecting eBay queues automatic listing discovery and catalogue matching. Scheduled eBay listing sweeps use the same durable queue. Refresh now is a recovery action when the automatic job needs another attempt.
  • Listing publish attempts keep enough history for interrupted remote publishes to be reviewed and reconciled. Interrupted attempts appear as Needs attention in Listing drafts and block another publish retry until ChannelWeave or an operator reconciles them.
  • Stock-consuming orders reduce available listing quantities. Website listings update immediately; external marketplaces continue through the channel sync queue.
  • A manually confirmed Discogs Order placed action uses the same reservation and fan-out path. Amazon, Shopify and WooCommerce receive the resulting quantity. When eBay availability reaches zero, its worker explicitly ends the Listing; an unsuccessful end remains visible as a queue failure.
  • Account-deletion and disconnect events are verified before account data is removed or scrubbed.

Health indicators

  • Queue depth
  • Retry count
  • Oldest pending age
  • Failure ratio by channel
  • Last successful sync time
  • Stuck or repeatedly failing jobs
  • Last error summary

Where to look

Discogs enrichment is a deliberate catalogue job rather than a connected Channel sync. Its health check measures time since an active run last made progress, not merely the age of its first queued record: warning begins after 30 minutes without progress and critical after two hours. A normal 50,000-item intake does not itself trigger a depth warning; the guardrails are 60,000 queued items for warning and 100,000 for critical. Paused/cancelled pending work is excluded. Review the run's remaining-work estimate alongside failures and progress before deciding that a large catalogue is stalled.

  • Control Centre: current connection state, last successful sync signals, recent issue counts, and automatic eBay listing sync state.
  • Events & diagnostics: event-by-event detail for channel actions, webhooks, and sync jobs.
  • Listings and Listing drafts: item-level publish and listing state. Listing drafts also shows the latest publish error or attention-required reconciliation message inline, so failed rows do not require opening one by one.
  • Orders: imported order state and downstream fulfilment impact.

Common causes of sync pressure

  • Expired or revoked channel authorisation.
  • Marketplace throttling or temporary provider outage.
  • A publish request that needs user correction before retry.
  • A listing or order payload that is missing required channel data.
  • Repeated manual retries before the previous job has finished.

Incident response

  1. Check the connection and the latest error in Events & diagnostics.
  2. Fix expired authorisation, provider availability, or item-data problems.
  3. Use Refresh now once to queue recovery work.
  4. Verify listing-to-stock matches and review any remaining exceptions.