> For the complete documentation index, see [llms.txt](https://docs.peakcommerce.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.peakcommerce.com/product/settings/billing-catalog/catalog-sync-history.md).

# Catalog Sync History

**Settings → Catalog Sync History** is the log of catalog sync runs between your billing provider and PeakCommerce — when each ran, what changed, and whether it succeeded. Use it to confirm a sync landed and to troubleshoot when your catalog looks wrong.

## Why it matters

Catalog syncs are how products, plans, and charges from your billing provider — Zuora, Stripe, or Metronome — become sellable in PeakCommerce. When something is missing, mispriced, or unexpectedly deactivated, this log is the first place to look — it tells you whether the last sync ran, what it touched, and whether it errored.

## What it shows

Each row is one sync run for one integration, with:

* **When** — start and finish time and duration.
* **What changed** — products, plans, and charges **synced**, plus anything **deactivated** or removed, and a count of products that came back with zero plans.
* **Status** — success, partial failure, or failed (with an error count).
* **Trigger source** — **manual** (you clicked sync), **scheduled** (background sync), or **drift watcher** (an automatic re-sync after [Catalog Drift](/product/settings/billing-catalog/catalog-drift.md) detected a gap).
* **Triggered by** — the operator who started a manual run.

Open a run for its full detail, including the per-product result payload.

## How to use it

* After a manual sync or an upstream change, confirm the latest row shows **success** and the expected counts.
* When a product or price looks stale, check whether the most recent run **failed** or skipped that product (zero plans), then re-sync or fix the upstream definition.
* Filter by integration, status, or trigger source to narrow down a problem run.

## Gotchas

* Older entries are pruned over time, but the most recent runs per integration are always kept — so a sparse history for a quiet integration is normal.
* A **partial failure** means some items synced and others errored; treat it like a failure for the affected products rather than a clean run.

## Related

* [Catalog Drift](/product/settings/billing-catalog/catalog-drift.md) — the watcher that triggers automatic re-syncs.
* [Billing Integration Cache](/product/settings/billing-catalog/billing-integration-cache.md) — the cached data syncs feed.
* [Products overview](/product/using-peakcommerce/products-and-bundles/products-overview.md)
* [Zuora billing integration](https://gitlab.com/peak-hercules/peak-help-docs/-/tree/main/integrations/zuora-integration/zuora-billing-integration.md)
* [Stripe integration](https://gitlab.com/peak-hercules/peak-help-docs/-/tree/main/integrations/stripe/stripe-payments.md)
* [Metronome integration](https://gitlab.com/peak-hercules/peak-help-docs/-/tree/main/integrations/metronome/metronome-usage-based-billing.md)


---

# 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.peakcommerce.com/product/settings/billing-catalog/catalog-sync-history.md?ask=<question>&goal=<endgoal>
```

`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.