> For the complete documentation index, see [llms.txt](https://docs.abtasty.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.abtasty.com/commerce/monitoring-deployment-health.md). # Monitoring deployment health The **Health monitor** is your single source of truth for the operational state of AB Tasty Commerce. It tracks every catalog **synchronization** and every strategy **deployment**, surfaces failures in plain language, and lets you relaunch a sync when something needs fixing. Open **Health monitor** in the left navigation. The **Health monitor** is your single source of truth for the operational state of AB Tasty Commerce. It tracks every catalog **synchronization** and every strategy **deployment**, surfaces failures in plain language, and lets you relaunch a sync when something needs fixing. Open **Health monitor** in the left navigation.
### Status banner The banner at the top of the page summarizes overall health and the freshness of your data: * **"Recommendations & Merchandising is working perfectly"**: the overall health message. When an operation fails, this message changes to flag the issue and provides links to investigate. * **Last successful synchronization**: for example, *"about 8 hours ago"*, when your catalog was last refreshed end-to-end. * **Last successful deployment**: for example, *"about 8 hours ago"*, when your strategies were last published live. {% hint style="info" %} **Synchronization** keeps the catalog and computed scores up to date. **Deployment** pushes a saved strategy version live. They are tracked separately because a healthy sync does not, on its own, publish strategy changes. {% endhint %} ### Your account status The **"Your account status"** section shows a status indicator for each Commerce module, so you can tell at a glance which area is affected when something goes wrong: | Indicator | What it covers | | ------------------- | --------------------------------------------------------------------------------------- | | **Catalog** | Retrieval, processing and generation of your product catalog. | | **Analytics** | Ingestion of analytics signals (pageviews, purchases, revenue) that enrich the catalog. | | **Recommendations** | Training and deployment of recommendation strategies. | | **Merchandising** | Computation of merchandising scores and category deployments. | | **Search** | Freshness of the search catalog and ranking configuration. | A green status means the module is operating normally; a non-green status points you to the module to investigate in the **Operations history** below. ### Launch synchronization Use the **Launch synchronization** button to trigger a full catalog synchronization on demand, for example, after fixing a feed issue or to pull fresh product data outside the scheduled window. {% hint style="info" %} Scheduled synchronization runs automatically at the recurrence defined in **Settings → Preferences**. {% endhint %} ### Investigating a failed operation When an operation fails, the banner flags it and the row in **Operations history** carries the details: 1. Locate the failed operation in the **Operations history** table. 2. Open the operation to see the **Additional info**, Commerce explains the root cause in human-readable terms, lists the impacted services, and offers retry or confirmation options. 3. Fix the underlying cause (see the [troubleshooting table](https://file+.vscode-resource.vscode-cdn.net/Users/didier/repos/abtasty/commerce/docs/commerce/08-monitoring-deployment-health/README.md#most-common-synchronization-errors) below). 4. Relaunch using **Launch synchronization**, or use the in-context retry / *"I fixed it"* action where offered. If the same error recurs twice, persists after your fix, or a synchronization runs longer than two hours, contact support. Provide the **operation ID**, the **synchronization timestamp**, and the **error message** shown in **Additional info**. ### Catalog stability protection (Volume Guard) To stop a corrupted or partial feed from wiping your live catalog, Commerce can block a synchronization when the number of products drops unexpectedly. This is the **Catalog stability protection** threshold, configured in **Settings → Preferences** under **Catalog & analytics synchronization**.
* **"Catalog stability protection"**: *"Define a threshold which will block synchronization if a sudden reduction in the number of products in the catalog is detected"*. You pick the deviation threshold (for example, for Shopify). * If a sync would reduce the catalog by more than the threshold (a common rule of thumb being a drop greater than **15%**), it is **blocked** and reported as a failed operation rather than being applied. * If the reduction is intentional (for example, a deliberate catalog cleanup), confirm the operation / request a force publish to let it through. ### Email notifications Commerce can alert you by email when a synchronization or deployment fails. Recipients are the **Priority contacts** configured in **Settings → Preferences → Alerting**, *"These users will be alerted by email if synchronization or deployment errors appears"*. Choose recipients from your account members via *"Choose email(s) from account members"*. Notification emails include a summary of the issue, an explanation, recommended actions, and a link back to the **Health monitor**. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.abtasty.com/commerce/monitoring-deployment-health.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.