Reading supplier Health and History
Overview tells you what your suppliers can answer. Health and History tell you what actually happened. They are the two tabs to open when someone asks whether a supplier connection is really working, and the answer has to be evidence rather than an impression.
Health — the daily heartbeat
- Open Connections → PromoStandards.
- Choose Health.
Screenshot: the Health heartbeat.
Pick a window with the Health date range control: 14, 30 or 60 days. Each supplier gets a row of one bar per day, coloured by the worst result that day, so a single bad run is visible rather than averaged away.
| Colour key | Meaning |
|---|---|
| succeeded | All service updates completed. |
| updated after retry | Updates completed, but only after a retry. |
| incomplete | Some information could not be updated. |
| failed | An update could not finish. |
| not checked | No supplier check was recorded that day. Before the day you connected, the bar reads Not connected yet. |
| in progress | An update is still running. |
Hover, focus or tap a day to open its detail: the date, which lane was used (Supplier account or Shared feed), and the day's counts — SUPPLIERS CHECKED, COMPLETED UPDATES, UPDATES WITH PROBLEMS, IN PROGRESS — plus any failures named service by service.
Four figures sit above the chart:
- SUPPLIERS UP TO DATE — all connected services passed a check within the last 24 hours.
- AWAITING AN UPDATE — suppliers with an unchecked, outdated or unsuccessful service check.
- ISSUES TO FIX — current supplier service problems; the action for each is listed below.
- DAYS WITHOUT ISSUES — the share of checked supplier days with no failed or incomplete updates.
Open issues
Under the chart, OPEN ISSUES lists each current problem with the supplier, a plain sentence, how long it has been going on, and a button that takes you to the thing that fixes it — usually the supplier's setup sheet or its credential request. When there is nothing, it says "No supplier connection issues need your attention."
Failure reasons are named in plain language: Credentials rejected, Rate limited, Timed out, Supplier service unavailable, Request rejected, Read position expired, Quota budget reached, Unclassified failure, or a warning such as Supplier subscription unavailable or Reconciliation pending.
History — what actually ran
- Choose History.
Screenshot: the History tab.
History covers the last 30 days. SUPPLIERS CHECKED PER DAY charts activity up to today, with the busiest day labelled. Its four figures are SUPPLIERS UPDATED (connected suppliers with at least one successful service update in the window), COMPLETED UPDATES, UPDATES WITH PROBLEMS (some of which may since have recovered) and SUPPLIERS UP TO DATE.
UPDATES is the table underneath, newest first, in your workspace time zone. One row is one supplier service update, with four columns:
- WHEN
- SUPPLIER
- SERVICE — order status, shipments, inventory, pricing, product data or invoices
- RESULT — UPDATED, WARNING, INCOMPLETE, FAILED, IN PROGRESS or NOT CHECKED
Each row also carries how it was triggered — Scheduled, Manual, Recovery, a PO check prompted by a purchase order Scout found in the mailbox, a Service check you ran yourself, or Maintenance — along with the calls it spent, the records it saw, how many were new and how long it took.
When there is nothing, History says "No supplier updates in the last 30 days." No history can mean no run happened. It does not mean a run happened and found nothing.
Runs, calls and records — three different things
- A run is one attempt to update one supplier service. One row in the table.
- A call is one request to the supplier's service. Every run spends calls from your workspace's daily allowance, which is why probing repeatedly is expensive rather than free.
- A record is something the service returned — an order, a shipment, a stock figure. Scout counts what it saw and how many were new to it.
A reused cached answer keeps its original age and does not claim the supplier was contacted again. If your daily allowance is spent, Check now cannot override it.
What to expect after connection
The configured rhythm is order status hourly, shipments every four hours, inventory twice a day, pricing weekly, and product data and invoices nightly, with one extra bounded check when a purchase order for that supplier turns up in authorized mail. The schedule runs only where it is enabled and admitted. Your permissions, the supplier's supported methods, how much work is already running and the calls left for the day can all delay a read. This is not a promise of real-time or complete supplier coverage.
Good to know
- Health explains a delay; History proves what was attempted. Use them in that order.
- A red incident is not repaired by reopening the page or waiting overnight. Scout needs a later valid check or run under the current authority.
- Health and History are for the whole workspace, and Owners and Admins manage what they show. Supplier connection problems reach administrators as notices, not as client work in anyone's Inbox.
- The Watch chips on Overview are coverage hints, not proof that a Watch ran — see Which Watches each supplier service powers.