> For the complete documentation index, see [llms.txt](https://ei-docs.keywordrush.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ei-docs.keywordrush.com/synchronizing-products/sync-status.md).

# Sync status page

Check whether External Importer is updating your products, which stores are blocked, and whether your synchronization settings can actually be met.

The **Sync status** page answers one question: is External Importer keeping your prices and stock up to date, and if not, why?

You can find it at:\
**External Importer → Sync status**

It is the fastest way to diagnose synchronization problems, and the first place to look before contacting support.

### The three panels at the top

**Synchronization** tells you whether products are being updated right now:

* **Working** – updates are running. The line below shows how many products are being updated at this moment, or when the last one was updated.
* **Not running** – nothing has been updated for a while, although your settings say it should be. See [Why prices don't update](/synchronizing-products/why-prices-dont-update.md).
* **Updated when viewed** – you are using Frontend synchronization, so products refresh as visitors open them.
* **Switched off** – the update period is set to *Disabled*.

**Waiting** shows how many products have passed their update period and are queued for an update. A number here is normal: products are updated gradually. What matters is whether it goes down over time.

**Last 7 days** shows how many products were updated successfully, and how many attempts failed.

### Settings

The **Settings** section repeats your current synchronization settings in one line so you can check them without leaving the page: update mode, update period, daily request limit per store, and how many products are under synchronization.

It also works out whether those settings can actually be met, and warns you when they cannot:

{% hint style="warning" %}
**domus.hr**: 4,200 products on this period need 600 requests a day, but the daily limit is 500. Raise the daily limit to 600, or set the update period to 9 days or more.
{% endhint %}

Two limits are checked:

* **The daily request limit for each store.** If a store has more products than its daily allowance can cover within your update period, those products can never keep up, no matter how long you wait.
* **How much this site can actually update in a day.** This is measured from how long updates have really taken on your server, so it accounts for slow sources and scraping services. Until enough updates have run, it shows *not enough history yet* rather than a guess.

### Stores

The table lists every store you import from, with:

* **Waiting** – products from this store whose update period has passed.
* **Failing** – products whose last update returned an error.
* **Last success** – when a product from this store was last updated successfully.
* **Updated (7 days)** – successful updates over the last week, with failures noted separately.
* **Today** – requests made to this store today, against its daily limit.
* **State** – whether the store is accepting requests:
  * **Active** – updating normally.
  * **Throttled** – too many errors from this store recently, so requests are paused for a while. It is retried automatically.
  * **Daily limit reached** – the store has used its whole daily allowance and resumes tomorrow.
  * **Waiting for budget** – the daily allowance is spread across the day, and this store has used its share so far. It resumes shortly.

Each row has an action: **Update now** for an active store, or **Reset throttle** for a store that has been paused, which clears its recorded errors so it can be tried again immediately.

{% hint style="info" %}
Throttling protects you. If a store is blocking your requests, continuing to hammer it usually makes the block worse. Fix the cause first – see [How to avoid getting blocked](/extracting-products/how-to-avoid-getting-blocked.md) – and use **Reset throttle** afterwards.
{% endhint %}

### Needs attention

Products that will not come right on their own:

* Products with **no store recorded**, which are skipped whenever another store is throttled.
* Products that were **paused** because updating them repeatedly failed to finish – usually a source that hangs until the request times out.
* Products that have **not been updated successfully for a long time**.

The **Repair** button fixes the first two categories: it fills in the missing store and lets paused products be tried again. On a large catalog it repairs up to 100 products per click, so run it again if there are more.

### Recent failures

The most recent failed updates, with the product, the error code and the message returned by the source store. **Retry failed products** queues every failing product for another attempt without waiting for its update period.

Common codes:

* **403** – the source is blocking your server. Use a [scraping service](/extracting-products/crawling-services.md).
* **404 / 410** – the product no longer exists at the source. It is marked Out of stock.
* **503** – the source is temporarily unavailable or rate limiting you.

### Buttons

* **Update products now** – adds the products that are due to the background queue. They are updated over the next few minutes, not while you wait.
* **Restart synchronization** – appears only when updates have stopped running. It re-registers the background task.

### Diagnostics

At the bottom of the page is a plain-text summary of everything above. If you contact support about synchronization, copy it into your message – it usually removes several rounds of questions.