Home Help centre Running a sync
Run a sync and read the result
A sync run reads your supplier's feed, compares it to your store, and writes only what changed. You can start one at any time with Sync now, and every run is recorded so you can see exactly what it did.
Start a sync
There are two places to start a run. On Connections, click Sync now on the supplier's row. Or open the connection and click Sync now, the primary action in the page header.
Everstock queues the run rather than performing it in your browser. From the list you get a toast reading Sync queued for <supplier>, and from the detail page it reads Sync queued. Clicking Sync now twice while the first run is still queued does not start a second one, because a queued sync is deduplicated per connection. A preview is queued separately from a real sync, so those two can wait side by side. Closing the page does not stop a run either. It continues and appears in Sync history when it finishes.
If the run cannot be queued at all, the connections list shows a critical banner instead of a toast, headed "Couldn't start the sync". The most common reason is a frozen subscription, which reads "Your plan is inactive. Reactivate it to run a sync." Starting the run from the connection page instead shows that same message as an error toast.
Watch it run
Stay on the connection detail page and you will see a Queued or Running badge while the sync waits or works, plus a "Sync running…" line with a spinner. When it finishes, the page refreshes itself and toasts Sync finished: Success (or Sync finished: Failed). The same Queued and Running badges appear at the top of Sync history.
That live watch gives up after about two minutes. If the run has not finished by then the spinner clears and a toast asks you to reload, for example "This sync is still waiting to start. Reload to check again, or contact support if it stays queued." The run itself is not cancelled. Reload the page, or open Sync history, to see where it got to.
The run then shows up in three places: Recent runs on the connection detail page, the full table on Sync history, and Recent sync runs on the dashboard. Note that the connections list's Last run column and the dashboard totals both exclude preview runs and supplier write-back runs.
If syncs sit in the queue for more than three minutes, a warning banner appears headed "Queued syncs have not started". It shows on the connection page, on Sync history, and on the dashboard, and it usually clears on its own.
Run statuses
A run is badged Success, Failed, Running, or Skipped. Running means it has started and has not finished yet. Skipped happens only when your subscription is frozen: the run is recorded with the note "Plan inactive. Sync skipped." A skipped run is not a failure and nothing in your store was touched.
The Run summary
Open a run and the page is headed "Run ·
Fetched is how many records Everstock read from the supplier feed. Applied is how many records it wrote to your store. Skipped is how many matched a product in your store and needed no change, which is the normal outcome for a record whose stock has not moved. For review is how many records a person needs to look at, such as a supplier row with no SKU or barcode, two rows sharing a key, or one of your products that was absent from the feed. Those are never written. Failed is how many writes did not go through.
On a preview, Applied is always 0, because a preview writes nothing. Its would-be changes appear in the run's audit table below the summary, each one badged Planned. You start a preview with Preview changes, which sits beside Sync now on the connection page and in the row's overflow menu on Connections.
Outcome banners
A preview carries an info banner headed "This run was a preview" with the line "Nothing was written to Shopify." A failed run carries a critical banner headed "Sync run didn’t complete", followed by the underlying messages. A run that finished but recorded something worth reading is headed "Sync run finished with notices", for example the note that it reached the 5,000-record audit cap.
The Fetch log
When a run made calls to your supplier, a Fetch log section follows the summary and lists them, with Endpoint, Duration, Rows, and Cache. Rows is how many records that entry returned. A feed split into several sub-feeds logs one entry per sub-feed. A feed read over several pages is logged once, as a single entry covering the whole read.
The Cache column badges Miss or Hit. Miss means Everstock fetched that data live from the supplier, which is what you will normally see. Hit means the run reused a recently fetched copy of the feed instead of calling the supplier again, so its duration reads 0 ms.
Dates
Every date and time in the admin is shown in UTC, with the zone printed after the time. The dashboard's activity chart repeats this as "Dates shown in UTC". A run started at 23:30 UTC therefore belongs to that UTC day, not to your local one.
Need help? Visit the support page or email hello@usenormalize.com.