Switches that stop an entire channel
Five things can silently disable synchronization completely. One is switched on automatically after five failed attempts.
Before debugging synchronization, check these five items. Each can silently disable the entire channel.
1. Two switches: listing downloads and stock publishing
The Stock and products stage has two separate cards, each with its own switch: Download listings at the top (read from the channel) and Stock synchronization below it (publish stock).
| Switch | What it controls | What it disables |
|---|---|---|
| Download listings from marketplace | whether we read this channel at all | listing downloads, ID synchronization, and full synchronization |
| Synchronize stock on marketplace | whether we publish stock to it | the stock publishing queue and manual publishing |
The dependency works in one direction. Stock is published for listings that have already been downloaded, so stock publishing works only when listing downloads are enabled. The screen will not save an invalid combination: with downloads off, the stock switch is locked; with stock publishing on, disabling downloads is locked. Turn stock publishing off first, then disable listing downloads.
The reverse is allowed: a channel from which you only download listings and to which you publish nothing is a valid configuration.
2. No active warehouse mapping
Without a mapping that has stock synchronization enabled, the channel is skipped when stock is published—without an error or a trace on screen (Mappings — warehouses, carriers, price lists, categories).
3. The connection is inactive
The unlabeled activity switch in the connection header stops everything that runs through it, including the price and attribute change queues.
4. A channel that keeps failing
After a failed download, the system does not disable the schedule. It backs off before retrying: 5, 10, 20, then 40 minutes, and finally no more than once an hour. When the cause is resolved, the channel automatically returns to its usual schedule.
After five consecutive errors, the connection is marked as an error on screens. The counter resets after the first successful download.
Symptom: the channel worked, started producing errors, and now downloads only rarely—about once an hour. Check the error counter and the last error message on the Download listings card.
5. A setting that does not exist
A setting without a saved value for your connection is invisible to the system. A task that checks it skips the connection, at most recording a warning in the log (Sales channel — integration, connection, and setting).
You cannot diagnose this in the panel; it looks exactly like missing configuration.
One more detail: a setting that behaves differently
The setting that disables fetching carrier statuses (fetch_trackings) responds only to the boolean value false. Entering the text value "false" does not disable anything, unlike other flags that accept both forms. If someone set it manually and it did not work, this is why.
Checks in order
- Is the connection active?
- Is Download listings from marketplace enabled—and, for stock issues, is Synchronize stock on marketplace enabled too?
- Is there an active warehouse mapping with stock synchronization enabled?
- Is the schedule enabled on the Download listings card?
- Does the product have a linked, active listing, if the channel requires one (Connected marketplaces and what each one cannot do)?
Only after these five checks should you inspect the queues (Synchronization is not working — checklist).
Want to see this with your orders? We’ll show you NOXTI with your sales channels and warehouse.
Book a demo