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 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 — the watcher that triggers automatic re-syncs.
Billing Integration Cache — the cached data syncs feed.
Last updated
Was this helpful?